| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Dann Corbit <DCorbit(at)connx(dot)com> |
| Cc: | Pgsql Group <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: About OIDs |
| Date: | 2003-03-28 01:39:21 |
| Message-ID: | 20030328013920.GB14905@svana.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Mar 27, 2003 at 01:44:06PM -0800, Dann Corbit wrote:
> They are very handy for our ODBC driver. It ensures that there is
> always some sort of unique identifier for any table, even if the
> designer did not create a primary key. (Sure, that's a naughty no-no,
> but it is astonishing how often it happens). At any rate, some complex
> joins can be sped up enormously by the existence of Odes.
OIDs are not necessarily unique. How do you handle that?
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> "the West won the world not by the superiority of its ideas or values or
> religion but rather by its superiority in applying organized violence.
> Westerners often forget this fact, non-Westerners never do."
> - Samuel P. Huntington
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2003-03-28 01:43:24 | Re: Python Error |
| Previous Message | Rupert | 2003-03-28 00:32:45 | Re: Cursors with Large, Ordered Result Sets |