af32c23768
A few minor things are fixed here. One is PostgreSQL, and more specifically pgbouncer, don't like it when the connection is closed after psycopg2 has started an implicit transaction even for read-only queries. Ensure we call commit as our last database action in all cases. The other is related- Django in management commands doesn't ever call close on any database connection you may have been using, so PostgreSQL gets mad about this fact and logs a message saying such. Close the connection explicitly when we are done with it to play nice. Signed-off-by: Dan McGee <dan@archlinux.org> |
||
---|---|---|
.. | ||
management | ||
migrations | ||
__init__.py | ||
admin.py | ||
fields.py | ||
forms.py | ||
models.py | ||
tests.py | ||
urls.py | ||
utils.py | ||
views.py |