From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Damon Cokenias <lists(at)mtn-palace(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: View INSERTs not returning OID in Postgres 7.2.1 |
Date: | 2002-04-11 02:10:07 |
Message-ID: | 25094.1018491007@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
Damon Cokenias <lists(at)mtn-palace(dot)com> writes:
> I recently moved from 7.1.3 to 7.2.1. In doing so, my application
> broke. It relies on INSERT returning the OID of the inserted row,
> even if the INSERT was on a view.
I'm afraid you were relying on a coincidental artifact of the old
implementation, namely that you got back the command tag associated
with the last command to be physically executed. The current code
is careful to return the command tag associated with the original
query (here, the insert into shadview) regardless of execution order
of additional queries executed by rules. I'm not sure that we can fix
your problem without breaking other cases.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | robert sanford | 2002-04-11 02:25:36 | which perl dbd module? |
Previous Message | P.J. "Josh" Rovero | 2002-04-11 01:41:47 | Re: Critical performance problems on large databases |
From | Date | Subject | |
---|---|---|---|
Next Message | Rajesh Kumar Mallah | 2002-04-11 06:34:51 | Re: Postgresql goes into recovery mode .... |
Previous Message | jeff fitzmyers | 2002-04-11 02:04:43 | Re: crypt question (search mail list) |