Re: [GENERAL] Unexpected Behavior Using a Rule With Multiple Actions (Long)

"James F. Hranicky" <[EMAIL PROTECTED]> writes: > What I'd really like to do is this: > create rule homes_update as on update to homes where OLD.fspath != > NEW.fspath do instead > ( > update homes_table set record_expired = now() where fsname > = OLD.fsn

[GENERAL] Unexpected Behavior Using a Rule With Multiple Actions (Long)

I'm attempting to set up a table that keeps it's own transaction history. Specifically, the table looks like this: create table homes_table ( fsname varchar(30), fspath varchar(40), record_added datetime default now(),