Tom Lane wrote:
> Right. I looked at this awhile back, though, and found multiple
> places that would break if you tried it :-( --- mainly assumptions
> about the meaning of resno in target lists. (The comments for the
> TargetEntry struct give some but not all of the details.) Given that
> OID
Martijn van Oosterhout writes:
> On Mon, Apr 10, 2006 at 04:40:50PM +0800, Qingqing Zhou wrote:
>> AFAIK if two rows are with the same OID, we will think these two rows are
>> different versions of the same tuple. So if we allow users to change OID
>> columns, we may encounter some inconsistency.
On Mon, Apr 10, 2006 at 04:40:50PM +0800, Qingqing Zhou wrote:
>
> "Peter Eisentraut" <[EMAIL PROTECTED]> wrote
> > Is there a reason for why you can't update the OID column other than that
> no
> > one has bothered to code up the support for it?
> >
>
> AFAIK if two rows are with the same OID, w
"Peter Eisentraut" <[EMAIL PROTECTED]> wrote
> Is there a reason for why you can't update the OID column other than that
no
> one has bothered to code up the support for it?
>
AFAIK if two rows are with the same OID, we will think these two rows are
different versions of the same tuple. So if we
Is there a reason for why you can't update the OID column other than that no
one has bothered to code up the support for it?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 9: In versions below 8.0, the pl
