From: Mike Bayer Date: Wed, 23 Nov 2011 00:01:21 +0000 (-0500) Subject: call the simply police X-Git-Tag: rel_0_7_4~52 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=3acf2ef25808c9e877089a2efa4d47e7b4776a59;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git call the simply police --- diff --git a/doc/build/core/tutorial.rst b/doc/build/core/tutorial.rst index 36fa476954..d347f05468 100644 --- a/doc/build/core/tutorial.rst +++ b/doc/build/core/tutorial.rst @@ -1522,7 +1522,7 @@ which updates one table at a time, but can reference additional tables in an add "FROM" clause that can then be referenced in the WHERE clause directly. On MySQL, multiple tables can be embedded into a single UPDATE statement separated by a comma. The SQLAlchemy :func:`.update` construct supports both of these modes -implicitly, simply by specifying multiple tables in the WHERE clause:: +implicitly, by specifying multiple tables in the WHERE clause:: stmt = users.update().\ values(name='ed wood').\ @@ -1555,7 +1555,7 @@ The tables are referenced explicitly in the SET clause:: SQLAlchemy doesn't do anything special when these constructs are used on a non-supporting database. The ``UPDATE FROM`` syntax generates by default -when multiple tables are present, and the statement will simply be rejected +when multiple tables are present, and the statement will be rejected by the database if this syntax is not supported. .. _deletes: