> inheriting pk and triggers
pg inheritance is quite limited. what i (and i'm sure many others)
have done is:
1. create master sequence
2. create base table
3. create base trigger procedures
4. create derived tables, using "inherit"
5. write procedure p( table_name ) that
a) sets pk of table_na
Stephan Szabo wrote:
On Wed, 29 Jan 2003, Neal Lindsay wrote:
I am creating a database that will keep track of several different types
of 'events'. I am toying with the idea of making a base 'class' table
for the tables because a lot of the information will be the same (also
there will probably b
On Wed, 29 Jan 2003, Neal Lindsay wrote:
> I am creating a database that will keep track of several different types
> of 'events'. I am toying with the idea of making a base 'class' table
> for the tables because a lot of the information will be the same (also
> there will probably be times I jus
I am creating a database that will keep track of several different types
of 'events'. I am toying with the idea of making a base 'class' table
for the tables because a lot of the information will be the same (also
there will probably be times I just need to get the basic information
about event
