diff options
| author | Ville Skyttä <ville.skytta@iki.fi> | 2016-10-07 13:18:58 +0300 |
|---|---|---|
| committer | Ville Skyttä <ville.skytta@iki.fi> | 2016-10-08 20:42:50 +0300 |
| commit | 8c2c464cb8e1b40f90f544295afbf9a83b372eb7 (patch) | |
| tree | 09a6c0d0f76f77c8de444fd60e0049a203de7966 /doc/build/faq | |
| parent | e47063bfe0de1318c12a4f9ef67b9538cad34489 (diff) | |
| download | sqlalchemy-8c2c464cb8e1b40f90f544295afbf9a83b372eb7.tar.gz | |
spelling: Postgresql -> PostgreSQL
Diffstat (limited to 'doc/build/faq')
| -rw-r--r-- | doc/build/faq/connections.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/build/faq/connections.rst b/doc/build/faq/connections.rst index 658b4f785..7e763d288 100644 --- a/doc/build/faq/connections.rst +++ b/doc/build/faq/connections.rst @@ -63,7 +63,7 @@ this is the default behavior of the Python database API, meaning it must be assumed that a transaction is always in progress. The connection pool issues ``connection.rollback()`` when a connection is returned. This is so that any transactional resources remaining on the connection are -released. On a database like Postgresql or MSSQL where table resources are +released. On a database like PostgreSQL or MSSQL where table resources are aggressively locked, this is critical so that rows and tables don't remain locked within connections that are no longer in use. An application can otherwise hang. It's not just for locks, however, and is equally critical on |