| From: | Evan Martin <postgresql(at)realityexists(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Plans to fix table inheritance caveats |
| Date: | 2011-10-18 04:57:36 |
| Message-ID: | 4E9D0740.4070507@realityexists.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
Are there any plans to fix the caveats documented in section 5.8.1,
particularly allowing rows in a derived table to satisfy a foreign key
defined on a base table? I know it's on the TODO list (
http://wiki.postgresql.org/wiki/Todo#Inheritance ) - just wondering if
anyone is actually working on it or planning to in the foreseeable future.
It would certainly be my number one feature request for PostgreSQL!
Table inheritance is very useful for persisting an object model with
inheritance, but with this limitation it can effectively only be used
when nothing references the base table (unless you give up referential
integrity).
Regards,
Evan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vishnu S. | 2011-10-18 06:16:47 | POstgreSQL Tablespace deletion issue |
| Previous Message | Martijn van Oosterhout | 2011-10-17 20:59:42 | Re: Video of Activity on PostgreSQL GIT repository |