#60: Document/solve possible issues regarding OIDs
-------------------------+-----------------
Reporter: cito | Owner:
Type: task | Status: new
Priority: major | Milestone: 5.0
Component: Classic API | Version: 4.1
Keywords: oids docs |
-------------------------+-----------------
PostgreSQL stopped adding OIDs to user tables by default since version
8.1.
However, the classic pg module still makes use of OIDs in several places.
We should document exactly where it relies on OIDs and what problems can
appear when your tables do not have OIDs. Maybe we can also improve the
classic pg module so that it becomes less dependent on OIDs. Should we
recommend setting `DEFAULT_WITH_OIDS=TRUE` when creating tables supposed
to work with the classic pg module? Note that there are certainly valid
reasons why OIDs have been deprecated for user tables.
See also
* [[http://stackoverflow.com/questions/5625585/sql-postgres-oids-what-are-
they-and-why-are-they-useful|Postgres OIDs: What are they and why are they
useful?]]
* [[http://www.revsys.com/blog/2006/jan/02/why-you-should-make-your-
postgresql-tables-without-oids/|Why you should make your PostgreSQL tables
without OIDs]]
* [[http://www.postgresql.org/docs/current/static/datatype-
oid.html|Postgres Docs: Object Identifier Types]]
--
Ticket URL: <http://trac.pygresql.org:8000/trac/ticket/60>
PyGreSQL <http://www.pygresql.org/>
PyGreSQL Tracker
_______________________________________________
PyGreSQL mailing list
[email protected]
https://mail.vex.net/mailman/listinfo.cgi/pygresql
