| From: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
|---|---|
| To: | "Aasmund Midttun Godal" <postgresql(at)envisity(dot)com>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: oid's in views. |
| Date: | 2001-10-19 15:07:50 |
| Message-ID: | web-151072@davinci.ethosmedia.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Aasmund,
> The oid column will always be blank. The oid column can never be used
> for anything usefull.
I believe the *official* reccommendation now is that you leave the OIDs
to the system, and create your own SERIAL values for row identification.
There are *lots* of problems with using OIDs as an index, and you've
just found one more!
-Josh
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh(at)agliodbs(dot)com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/plain | 2 bytes |
| unknown_filename | text/plain | 2 bytes |
| unknown_filename | text/plain | 2 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2001-10-19 17:46:50 | Re: system maintained keys |
| Previous Message | Pat M | 2001-10-19 12:56:02 | Re: Deleting obsolete values |