Looking at the code, it seems like db_pool is created at import to properly proxy to the sqlalchemy pool manager as expected.
However, as of the changeset in https://github.com/kennethreitz/django-postgrespool/pull/21 it seems like the db_pool is no longer used to connect to the database and it should fallback to the default django psycopg2 drivers.
The only reference to the db_pool object that should do the pooling magic is in the _dispose method. So it seems like this is a simple wrapper around the default Django backend.
Perhaps I am missing some DB-API knowledge or Django magic though?
Looking at the code, it seems like
db_poolis created at import to properly proxy to the sqlalchemy pool manager as expected.However, as of the changeset in https://github.com/kennethreitz/django-postgrespool/pull/21 it seems like the
db_poolis no longer used to connect to the database and it should fallback to the default django psycopg2 drivers.The only reference to the
db_poolobject that should do the pooling magic is in the_disposemethod. So it seems like this is a simple wrapper around the default Django backend.Perhaps I am missing some DB-API knowledge or Django magic though?