From: Josh Berkus <josh@agliodbs.com>
To: Aasmund Midttun Godal <postgresql@envisity.com>
To: pgsql-sql@postgresql.org
Subject: Re: oid's in views.
Date: Fri, 19 Oct 2001 08:07:50 -0700
Message-ID: <web-151072@davinci.ethosmedia.com> (raw)
In-Reply-To: <20011019030149.23206.qmail@ns.krot.org>
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@agliodbs.com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com, postgresql@envisity.com
Subject: Re: oid's in views.
In-Reply-To: <web-151072@davinci.ethosmedia.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox