You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/tutorial/where.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -311,7 +311,7 @@ Instead, it results in a special type of object. If you tried that in an interac
311
311
<sqlalchemy.sql.elements.BinaryExpression object at 0x7f4aec0d6c90>
312
312
```
313
313
314
-
So, that result value is an **expession** object. 💡
314
+
So, that result value is an **expression** object. 💡
315
315
316
316
And `.where()` takes one (or more) of these **expression** objects to update the SQL statement.
317
317
@@ -421,7 +421,7 @@ Of course, the keyword arguments would have been a bit shorter.
421
421
422
422
But with the **expressions** your editor can help you a lot with autocompletion and inline error checks. ✨
423
423
424
-
Let me give you an example. Let's imagine that keword arguments were supported in SQLModel and you wanted to filter using the secret identity of Spider-Boy.
424
+
Let me give you an example. Let's imagine that keyword arguments were supported in SQLModel and you wanted to filter using the secret identity of Spider-Boy.
425
425
426
426
You could write:
427
427
@@ -436,7 +436,7 @@ Maybe your code could even run and seem like it's all fine, and then some months
436
436
437
437
And maybe finally you would realize that we wrote the code using `secret_identity` which is not a column in the table. We should have written `secret_name` instead.
438
438
439
-
Now, with the the expressions, your editor would show you an error right away if you tried this:
439
+
Now, with the expressions, your editor would show you an error right away if you tried this:
0 commit comments