Hello Mike. > On 6 Feb 2018, at 16:24, Mike Bayer <mike...@zzzcomputing.com> wrote: > > it is unusual for people to use the pool without an engine like that. > You can always get a pool by creating an engine normally and then > grabbing engine.pool. When the engine is created one of the things > it does is load up the DBAPI for the dialect. if you want to do that > manually, it looks like:
Thanks for the help. I'm using the package django_postgrespool2 so I'm currently not in control of how the pool is instantiated. The package does this: In https://github.com/lcd1232/django-postgrespool2/blob/master/django_postgrespool2/base.py <https://github.com/lcd1232/django-postgrespool2/blob/master/django_postgrespool2/base.py> from sqlalchemy.pool import manage ... POOL_SETTINGS = 'DATABASE_POOL_ARGS' pool_args = getattr(settings, POOL_SETTINGS, {}) db_pool = manage(Database, **pool_args) So it's only using SQLAlchemy''s pool functionality to manage Django DB connections. I guess I just have to pass the "dbapi=psycopg2" parameter when creating the dialect? Best regards, André -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
