On Dec 31, 2005, at 6:39 PM, Jonathan Ellis wrote:
Foo.get(1)
dies complaining of oid absence. Seems strange that get doesn't
use a known PK.
also that is weird because there are plenty of get()'s in the unit
tests which I run all the time against postgres, and also I am not
doing anything with that "WITH OID" clause that doc mentions. is it
postgres giving you the error ? Id be curious to see what its asking
the DB for, if you turn echo=True on the engine, and also you can add
the keyword argument "order_by=None" to all mapper() functions and it
should stop trying to use the oid. ill look into a way to globally
disable the usage of all oids for ordering.
-------------------------------------------------------
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
