From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
Cc: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, PostgreSQL HACKERS <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: postgres TODO |
Date: | 2000-07-13 07:13:19 |
Message-ID: | 28609.963472399@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> At 11:05 12/07/00 +0200, Jan Wieck wrote:
>> Tom Lane wrote:
>>>
>>> Philip's INSERT ... RETURNING idea could support returning TID and
>>> table OID as a special case, and it has the saving grace that it
>>> won't affect apps that don't use it...
> What sort of syntax would you use to request TID?
... RETURNING ctid
This might be a little tricky; you'd have to be sure the RETURNING
code executes late enough that a TID has been assigned to the tuple.
Not sure if post-insert trigger time is late enough or not (Jan?)
but in principle it's not a special case at all, just a system
attribute the same as OID.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Bitmead | 2000-07-13 07:17:12 | OO enhancements |
Previous Message | Zeugswetter Andreas SB | 2000-07-13 07:11:30 | AW: Some Improvement |