From d69407abdb6e89183b69696ca9f873e268ddb3af Mon Sep 17 00:00:00 2001 From: =?utf8?q?Sebasti=C3=A1n=20Ram=C3=ADrez?= Date: Wed, 28 Apr 2021 20:42:07 +0200 Subject: [PATCH] =?utf8?q?=E2=9C=8F=EF=B8=8F=20Fix=20typos=20in=20"Data=20?= =?utf8?q?Manipulation=20with=20the=20ORM"=20(#6389)?= MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit --- doc/build/tutorial/orm_data_manipulation.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/build/tutorial/orm_data_manipulation.rst b/doc/build/tutorial/orm_data_manipulation.rst index 6068ec4fd4..740880567f 100644 --- a/doc/build/tutorial/orm_data_manipulation.rst +++ b/doc/build/tutorial/orm_data_manipulation.rst @@ -316,10 +316,10 @@ a value in the ``User.name`` column: >>> session.execute( ... update(User). ... where(User.name == "sandy"). - ... values(fullname="Sandy Squirrel Extraodinaire") + ... values(fullname="Sandy Squirrel Extraordinaire") ... ) {opensql}UPDATE user_account SET fullname=? WHERE user_account.name = ? - [...] ('Sandy Squirrel Extraodinaire', 'sandy'){stop} + [...] ('Sandy Squirrel Extraordinaire', 'sandy'){stop} When invoking the ORM-enabled UPDATE statement, special logic is used to locate @@ -328,7 +328,7 @@ are refreshed with the new data. Above, the ``sandy`` object identity was located in memory and refreshed:: >>> sandy.fullname - 'Sandy Squirrel Extraodinaire' + 'Sandy Squirrel Extraordinaire' The refresh logic is known as the ``synchronize_session`` option, and is described in detail in the section :ref:`orm_expression_update_delete`. -- 2.47.3