| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Albert Cervera Areny <albertca(at)hotpop(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Inheritance, Primary Keys and Foreign Keys |
| Date: | 2006-05-09 19:43:30 |
| Message-ID: | 1147203811.4572.48.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2006-05-09 at 01:20 +0200, Albert Cervera Areny wrote:
> In my particular case (don't know about the SQL standard or other cases),
> it'd be enough if when an inherited table is created:
> - A primary key in the inherited table is created with the same columns as
> the super table.
> - A trigger is created in the new table that ensures that this primary key
> doesn't exist in the super table.
> - A trigger is created in the super table that ensures that this primary key
> doesn't exist in it's sub tables.
Why not add these in your design rather than into the database?
All of the above can be added using existing DDL and you can group
things together in a transaction and call when required.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2006-05-09 20:37:04 | [PATCH] Improve EXPLAIN ANALYZE overhead by sampling |
| Previous Message | Tom Lane | 2006-05-09 19:13:01 | Re: [HACKERS] Big IN() clauses etc : feature proposal |