From: | "Gerard Mason" <gerardmason(at)hotmail(dot)com> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Abstract base table? |
Date: | 2003-12-02 14:46:41 |
Message-ID: | BAY7-F17DjFbUcOV1Ee000027f0@hotmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
I am toying with the idea of deriving a couple of tables from a common table
(though I am aware that there are some oddities with the way postgresql does
inheritance). It should be possible to make entries into the derived tables,
but not into the base table (because it really just doesn't have enough
columns to be viable).
Ignoring questions as to the advisability of the design, is it possible to
check in a rule or a trigger function, which table it is exactly that is
being updated, the base or the derived?
Cheers,
Gerard.
_________________________________________________________________
Find a cheaper internet access deal - choose one to suit you.
http://www.msn.co.uk/internetaccess
From | Date | Subject | |
---|---|---|---|
Next Message | Taylor Lewick | 2003-12-03 02:44:04 | relationship/table design question |
Previous Message | Bruce Momjian | 2003-12-01 15:54:05 | Re: Migration to version 7.4 |