Michael Bayer wrote:
try turning on echo=True when you make the DBengine, it will show you
all the queries as well as their results sent to standard out.
its *possible* that something goes wrong with the toengine() call with
sqlite, try hardcoding your engines to a plain sqlite engine, i.e. dont
use a non-sqlite engine at all, and see if that fixes it.
It happens even with a hard-coded sqlite engine. All the select queries are
prefixed with the table name, e.g. 'select foo.id, foo.col1...' for both
postgres and sqlite, but the cursor.description used in the ResultProxy
constructor is different, i.e. sqlite's metadata has the table name prepended to
the column name in item[0].
Is this a version issue - I'm using the latest pysqlite (2.0.5) and psycopg
v2.0b1? (although that doesn't explain why the SQLAlchemy unit tests are working).
Robert
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Sqlalchemy-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
