Hi -
I too have encountered this issue. The work around that I created was to
have every table have a set of 3 cooresponding functions that know how to
1) create the table; 2) create triggers for the table; 3) create indexes
for the table. By doing so, I then am able to use a lazy
Hi,
Am Freitag, 23. Feb 2007, 07:10:06 + schrieb Richard Huxton:
Bertram Scharpf wrote:
it is very inconvenient for me that triggers aren't inherited:
Foreign keys too (which are a special type of trigger of course).
Is this behaviour to be implemented at any point of time in
the
Hi,
it is very inconvenient for me that triggers aren't inherited:
create table watch (
mod timestamp with time zone default '-infinity' not null
);
create function update_mod() returns trigger ...
create trigger update_mod before insert or update on watch
for each row
Bertram Scharpf wrote:
Hi,
it is very inconvenient for me that triggers aren't inherited:
Foreign keys too (which are a special type of trigger of course).
Is this behaviour to be implemented at any point of time in
the future? Could it be advisible to write the patch? Or is
it just too
