Re: oids vs composite types, in cvs head
От | Andrew - Supernews |
---|---|
Тема | Re: oids vs composite types, in cvs head |
Дата | |
Msg-id | slrndcmk02.evl.andrew+nonews@trinity.supernews.net обсуждение исходный текст |
Ответ на | oids vs composite types, in cvs head (Andrew - Supernews <andrew+nonews@supernews.com>) |
Список | pgsql-hackers |
On 2005-07-06, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Andrew - Supernews <andrew+nonews@supernews.com> writes: >> This works on 7.4 and 8.0 but not in cvs head: >> create function foo(pg_type) returns oid as 'select $1.oid' language sql; >> ERROR: column "oid" not found in data type pg_type >> CONTEXT: SQL function "foo" > >> Is this intentional, or did the no-oids-by-default changes cut too deep? > > Hmm ... offhand, I'd say that if it worked in 8.0 it was only by chance. > In general a tuple that matches the signature of a pg_type row need not > contain an OID. Still it does seem that we have broken some specific > cases that used to work. Anyone want to dig into the details? I think this is what changed it: http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_func.c.diff?r1=1.176;r2=1.177 -- Andrew, Supernews http://www.supernews.com - individual and corporate NNTP services
В списке pgsql-hackers по дате отправления: