diff options
| author | Alex Gaynor <alex.gaynor@gmail.com> | 2014-04-26 13:13:13 -0700 |
|---|---|---|
| committer | Alex Gaynor <alex.gaynor@gmail.com> | 2014-04-26 13:13:13 -0700 |
| commit | 1caa7fafbd3c9870e1bf2b2ac623872447fc804e (patch) | |
| tree | 509f53bfba7c3bbc6941653b82c7cefcb819247c /doc/build/glossary.rst | |
| parent | 146fbf6d26a8c4140a47aeb03131fdf81007b9a2 (diff) | |
| download | sqlalchemy-1caa7fafbd3c9870e1bf2b2ac623872447fc804e.tar.gz | |
Fix many typos throughout the codebasepr/85
Found using: https://github.com/intgr/topy
Diffstat (limited to 'doc/build/glossary.rst')
| -rw-r--r-- | doc/build/glossary.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/build/glossary.rst b/doc/build/glossary.rst index cd6f87f29..ab9e92d26 100644 --- a/doc/build/glossary.rst +++ b/doc/build/glossary.rst @@ -387,7 +387,7 @@ Glossary A subquery comes in two general flavors, one known as a "scalar select" which specifically must return exactly one row and one column, and the other form which acts as a "derived table" and serves as a source of - rows for the FROM clause of another select. A scalar select is eligble + rows for the FROM clause of another select. A scalar select is eligible to be placed in the :term:`WHERE clause`, :term:`columns clause`, ORDER BY clause or HAVING clause of the enclosing select, whereas the derived table form is eligible to be placed in the FROM clause of the @@ -447,7 +447,7 @@ Glossary The above subquery refers to the ``user_account`` table, which is not itself in the ``FROM`` clause of this nested query. Instead, the ``user_account`` - table is recieved from the enclosing query, where each row selected from + table is received from the enclosing query, where each row selected from ``user_account`` results in a distinct execution of the subquery. A correlated subquery is in most cases present in the :term:`WHERE clause` |
