summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2007-08-06 16:23:03 +0000
committerMike Bayer <mike_mp@zzzcomputing.com>2007-08-06 16:23:03 +0000
commitba701cde75357a84099cc7bbdf0f0dde8d717e78 (patch)
treed96d6622b7ebe2c1dd729cd28982b1bb1280a2a8 /doc
parentcf9549854fb1e1e09128b30e9cada480d27761e3 (diff)
downloadsqlalchemy-ba701cde75357a84099cc7bbdf0f0dde8d717e78.tar.gz
edits
Diffstat (limited to 'doc')
-rw-r--r--doc/build/content/sqlexpression.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/build/content/sqlexpression.txt b/doc/build/content/sqlexpression.txt
index e623ca83f..9b35b2f23 100644
--- a/doc/build/content/sqlexpression.txt
+++ b/doc/build/content/sqlexpression.txt
@@ -368,9 +368,9 @@ So with all of this vocabulary, let's select all users who have an email address
WHERE users.id = addresses.user_id AND users.name BETWEEN ? AND ? AND
(addresses.email_address LIKE ? OR addresses.email_address LIKE ?)
[', ', 'm', 'z', '%@aol.com', '%@msn.com']
- {stop}[(u'Wendy Williams, wendy@aol.com',)]
+ [(u'Wendy Williams, wendy@aol.com',)]
-Once again, SQLAlchemy figured out the correct FROM clause for our statement. In fact it will determine the FROM clause based on all of its other bits; the columns clause, the whereclause, and also some other elements which we haven't covered yet, which include ORDER BY, GROUP BY, and HAVING. In the above case both the `users` and `addresses` table were mentioned plenty of times so they came out just fine.
+Once again, SQLAlchemy figured out the FROM clause for our statement. In fact it will determine the FROM clause based on all of its other bits; the columns clause, the whereclause, and also some other elements which we haven't covered yet, which include ORDER BY, GROUP BY, and HAVING.
## Using Text {@name=text}