From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "dima Q" <dimaqq(at)gmail(dot)com>, <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: pgadmin3 doesn't list oid in columns |
Date: | 2004-11-16 09:49:04 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E430715F@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
> -----Original Message-----
> From: pgadmin-support-owner(at)postgresql(dot)org
> [mailto:pgadmin-support-owner(at)postgresql(dot)org] On Behalf Of dima Q
> Sent: 15 November 2004 19:41
> To: pgadmin-support(at)postgresql(dot)org
> Subject: [pgadmin-support] pgadmin3 doesn't list oid in columns
>
> Pgadmin3 doesn't seem to think of oid as a column in a table
> created "with oids".
>
> The consequences of this are:
> oid cannot be used when making constraints PK, FK, UNIQUE,
> etc in table modification dialog oid cannot be used when
> creating constraints in the constraint dialog oid cannot be
> used when making indices with pgadmin3
>
> I created oid-related constraints, indices etc. by hand and
> they can be viewed by pgadmin3 though.
>
> Is this a misfeature or you disabled such functionality on
> purpose because it can be seen as "bad style" in postresql?
Hi,
The oid column is classed as a system column, and as such is only
visible with 'View System Objects' turned on. You should not use this
column in your databases unless you have a very specific reason - one
very good reason not to use them is that OIDs are not necessarily
included in database dumps, therefore referential integrity might be
broken if you restore such a dump and had used the OID column in foreign
keys. There are also potential problems with OID-wraparound on large
databases.
Instead, I would suggest using a serial column as your PK etc. in all
your tables.
Regards, Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Walter Haslbeck | 2004-11-16 13:44:53 | pgadmin crashes on SuSE 9.2/wxGTK 2.5.3 |
Previous Message | Dave Page | 2004-11-16 09:43:11 | Re: SQL query error |