Re: Any reason why the default_with_oids GUC is still there?
От | Bruce Momjian |
---|---|
Тема | Re: Any reason why the default_with_oids GUC is still there? |
Дата | |
Msg-id | 201009221617.o8MGH8E25352@momjian.us обсуждение исходный текст |
Ответ на | Re: Any reason why the default_with_oids GUC is still there? (Peter Eisentraut <peter_e@gmx.net>) |
Список | pgsql-hackers |
Peter Eisentraut wrote: > On tis, 2010-09-21 at 18:31 -0400, Bruce Momjian wrote: > > Also, doesn't some SQL standard require oids, so we should have a way > > to enable them by default for all tables? > > >From some DB2 example: > > CREATE TYPE BusinessUnit_t AS > (Name VARCHAR(20), > Headcount INT); > > CREATE TABLE BusinessUnit OF BusinessUnit_t > (REF IS oid USER GENERATED); > > The DB2 documentation consistently refers to this column as "oid", but > there is no requirement to name it that way. > > The SQL standard also contains this sentence: > > Let OID be the name of the self-referencing column of S. > > which refers to the thing defined in the example above, but "OID" is > just a placeholder here. > > I think there was a mention of OIDs in the "SQL3" draft that eventually > became SQL99, but that's long past now. Current standards don't have > it, except in the, perhaps more generalized, form above. Thanks for those details. I did remember it appearing at one point, which I guess was SQL3. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
В списке pgsql-hackers по дате отправления: