[Sqlalchemy-tickets] [sqlalchemy] #1691: Compatibility problems with PyGreSQL
Brought to you by:
zzzeek
From: sqlalchemy <mi...@zz...> - 2010-02-15 20:13:42
|
#1691: Compatibility problems with PyGreSQL ----------------------+----------------------------------------------------- Reporter: guest | Owner: zzzeek Type: defect | Status: new Priority: medium | Milestone: Component: postgres | Severity: no triage selected yet Keywords: pygresql | Status_field: awaiting triage ----------------------+----------------------------------------------------- In the SQLAlchemy 0.5 branch, the method get_default_schema_name() in databases.postgres has the following code: {{{ return connection.scalar("select current_schema()", None) }}} This results in the DBAPI execute method being called with parameters set to `[None]` which is not expected here since the operation takes no parameters. It seems psycopg2 silently ignores this, but other drivers such as !PyGreSQL raise an exception. It would be nice if this could be fixed (by removing the None parameter, see patch), because it seems to be the only problem that prevents SQLAlchemy from working with !PyGreSQL properly. In the SQLAlchemy 0.6 branch this is implemented correctly already, but this branch does not work with !PyGreSQL any more (I tried setting `module=pgdb`, `creator=pgdb.connect`, and using `postgresql+pygresl://...` in the url). -- Christoph Zwerschke -- Ticket URL: <http://www.sqlalchemy.org/trac/ticket/1691> sqlalchemy <http://www.sqlalchemy.org/> The Database Toolkit for Python |