From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | Zhidian Du <duzhidian(at)hotmail(dot)com> |
Cc: | <pgsql-php(at)postgresql(dot)org>, <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: [SQL] Parent table has not oid? |
Date: | 2002-11-12 17:12:39 |
Message-ID: | Pine.LNX.4.33.0211121011440.24725-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-php pgsql-sql |
On Sun, 10 Nov 2002, Tom Lane wrote:
> "Zhidian Du" <duzhidian(at)hotmail(dot)com> writes:
> > CREATE TABLE Link (
> > Protein_ID oid
> > CONSTRAINT one
> > REFERENCES Protein (oid)
> > ON DELETE CASCADE,
> > Link varchar(128)
> > );
> > When I insert a record into this child table, it says
> > "ERROR: constraint one: table protein does not have an attribute oid"
>
> How old is your Postgres?
>
> IIRC, this was made to work in 7.2 or thereabouts.
>
> Note that using OID as a foreign key is not really a good idea, because
> it's problematic to dump and restore. You'd be better off with a serial
> column as primary key.
Yeah, I found that out the hardway and spent a couple days rewriting an
app that had used OIDs in a way it really shouldn't have.
The only time I use OIDs now is to get rid of duplicate rows by hand or
such like that.
From | Date | Subject | |
---|---|---|---|
Next Message | Fernando Papa | 2002-11-12 18:49:11 | Retriving cursor from pgplsql function |
Previous Message | Kevin Gordon | 2002-11-12 10:19:23 | Compiling Postgresql --with-unixodbc |
From | Date | Subject | |
---|---|---|---|
Next Message | Luis Sousa | 2002-11-12 17:12:45 | Re: Permission on insert rules |
Previous Message | Luis Sousa | 2002-11-12 17:10:32 | Re: Permission on insert rules |