From: Gabriel Izoton Date: Fri, 4 Aug 2023 17:48:41 +0000 (-0300) Subject: [docs] Typo: Update session_transaction.rst (#10185) X-Git-Tag: rel_2_0_20~19 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1377f33075a0e4230c88506d2bfd1e847a336da5;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git [docs] Typo: Update session_transaction.rst (#10185) Fixed typo: `tranasction` -> `transaction` --- diff --git a/doc/build/orm/session_transaction.rst b/doc/build/orm/session_transaction.rst index cb0f0fac24..85d1cf50be 100644 --- a/doc/build/orm/session_transaction.rst +++ b/doc/build/orm/session_transaction.rst @@ -175,7 +175,7 @@ an error is raised, the savepoint is rolled back and the state of the This pattern is ideal for situations such as using PostgreSQL and catching :class:`.IntegrityError` to detect duplicate rows; PostgreSQL normally -aborts the entire tranasction when such an error is raised, however when using +aborts the entire transaction when such an error is raised, however when using SAVEPOINT, the outer transaction is maintained. In the example below a list of data is persisted into the database, with the occasional "duplicate primary key" record skipped, without rolling back the entire