From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
---|---|
To: | BARTKO, Zoltán <bartko(dot)zoltan(at)pobox(dot)sk> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: foreign key problems |
Date: | 2005-01-05 13:29:29 |
Message-ID: | 20050105052001.T60967@megazone.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Wed, 5 Jan 2005, [iso-8859-2] BARTKO, Zoltán wrote:
> Ok, so I made some changes (manual "inheritance" of PK and FK
> constraints), but nevertheless I get still the same dumb error. I made
> a dump of the DB via pg_dump, it is available at
>
> http://de.geocities.com/bartkozo/dump.tgz
>
> DRecord was dropped, the columns moved into DObject. I still have no
> idea why foreign keys work on other tables and do not on this one.
>
> I have three users, superaspiramus, aspiramus and aspiramusadmin. The
> first is the owner of the db.
>
> After loading, the contents of the DObject table are:
>
> aspiramus=> select * from DObject;
Do select * from ONLY DObject.
The constraint currently only goes to DObject, records that are actually
in DObject and not any tables derived from it. This is one of the
deficiencies I was trying to refer to in the previous message. As a note,
your primary keys will also not work to prevent duplicates of objectid
between subclasses of DObject currently, and I'm not sure whether that
matters to you:
insert into dmessage (who, privilege, objectid, objecttype, status,
aname,sender,receiver) values (-2,-2,33,13,301,'name',-2,-2);
select objectid from dobject;
objectid
----------
34
35
33
33
(4 rows)
Inheritance needs alot of work. :(
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2005-01-05 13:32:54 | Re: foreign key problems |
Previous Message | CoL | 2005-01-05 12:50:42 | Re: Calling a table residing in another database from Plpgsql |