Martijn van Oosterhout wrote:
It means using OIDs as you described has very well known problems and
they will break on you eventually. You can mitigate the damage by
creating a UNIQUE index on the oid column but you'd better be sure your
application can handle the side-effects.
Ok, Tom told me about the same :-( But why are oid's still in PG, that
are they good for ? Will there be a real unique row id, like there is in
Oracle, or will this be keept as an internal value only ?
OIDs won't become obsolete, but they'll probably no longer be enabled
by default at some stage.
Is this because some old application's using oid's in somewhat small
dataset ?
Hope this helps,
It did thanks.
/BL
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
message can get through to the mailing list cleanly
