From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Jeff Davis <jdavis-pgsql(at)empires(dot)org> |
Cc: | Lonni J Friedman <netllama(at)gmail(dot)com>, PgSQL General List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: disabling OIDs? |
Date: | 2005-01-02 13:24:39 |
Message-ID: | 20050102132438.GA19311@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Jan 01, 2005 at 06:35:30PM -0800, Jeff Davis wrote:
> On Sun, 2004-12-12 at 20:25 -0800, Lonni J Friedman wrote:
> > OK, thanks. So is there any real benefit in doing this in a generic
> > (non-dspam) sense, or is it just a hack that wouldn't be noticable?
> > Any risks or potential problems down the line?
> >
> I'd just like to add that some 3rd party applications/interfaces make
> use of OIDs, as a convenient id to use if there is no primary key (or if
> the 3rd party software doesn't take the time to find the primary key).
>
> One might argue that those 3rd party applications/interfaces are broken,
> but you still might want to keep OIDs around in case you have a use for
> one of those pieces of software.
Yep, especially since an OID is not a unique value and so can't
possibly be a primary key and generally isn't indexed either. Even
Access asks you to identify the primary key...
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.
From | Date | Subject | |
---|---|---|---|
Next Message | Madison Kelly | 2005-01-02 14:54:35 | Re: Question on a select |
Previous Message | Sim Zacks | 2005-01-02 12:20:04 | citext datatype |