I'd like clarification on the use of OID's with Postgres and SQLAlchemy. Please
set me straight if I'm wrong:
1. OID's are deprecated from pg 8.1 and in fact it is the default to create
tables without OID's in that version on.
2. By default OID support is turned off in SQLAlchemy, but this has no impact on
the create table statements issued by the postgres engine - which means that
in a pre-8.1 database the tables are still created with OID's regardless of the
use_oid setting.
3. Inserting entries into a Postgres table in SQLAlchemy *requires* either an
OID or a sequence and this sequence *must* be the primary key. This is the case
even if only low level SQLAlchemy (i.e. no ORM/data mapping) is being used.
If 2 is true is it a good idea to extend the use_oid support to turnoff OID's
when creating tables and not let the backend use its default?
If 3 is true, isn't this too limiting, e.g what if I don't want artificial
primary keys and I don't want to use a deprecated feature? Also, how will
autoload work for existing tables that don't meet this criteria?
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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
