Re: RESULT_OID Bug
От | Kevin McArthur |
---|---|
Тема | Re: RESULT_OID Bug |
Дата | |
Msg-id | 00d101c5923a$eb20f010$0701a8c0@kdesktop обсуждение исходный текст |
Ответ на | RESULT_OID Bug ("Kevin McArthur" <postgresql-list@stormtide.ca>) |
Список | pgsql-hackers |
I cannot repoduce your experience with this bug. No matter what I do, reconnect session or otherwise, it never returns a proper oid on the newer cvs vers (I suspect it may be related to the roles update) Kevin ----- Original Message ----- From: "Michael Fuhr" <mike@fuhr.org> To: "Kevin McArthur" <postgresql-list@stormtide.ca> Cc: <pgsql-hackers@postgresql.org> Sent: Tuesday, July 26, 2005 4:19 PM Subject: Re: [HACKERS] RESULT_OID Bug > On Tue, Jul 26, 2005 at 03:36:26PM -0700, Kevin McArthur wrote: >> Recent cvs versions are failing the following script; >> >> create table oidtest(a time default now()) with oids; >> >> CREATE OR REPLACE FUNCTION oidtest() RETURNS integer AS $oidtest$ >> DECLARE >> insert_oid_var INTEGER; >> BEGIN >> INSERT INTO oidtest DEFAULT VALUES; >> GET DIAGNOSTICS insert_oid_var = RESULT_OID; >> RETURN insert_oid_var; >> END; >> $oidtest$ Language plpgsql; >> >> select oidtest(); >> >> if its working you will see an oid, if its failing you will see 1 row >> with blank data. > > The function appears to work in a session until you replace it (or > drop and recreate it), after which you get NULL. If you exit the > session and reconnect then it works again. I checked 8.0.3 and it > doesn't have this problem. > > -- > Michael Fuhr > http://www.fuhr.org/~mfuhr/ > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly >
В списке pgsql-hackers по дате отправления: