FW:

Posted in 2001

Topics: Server Administration, Triggers, Constraints & Referential Integrity

Lewis, Keith A. — Wed, 3 Jan 2001 15:59:33 -0500 — source: Informix-list mailing list archive (1991-1998)

Nevermind, I figured out the problem. Triggers never run on SMI tables. > -----Original Message----- > From: Lewis, Keith A. > Sent: Wednesday, January 03, 2001 3:32 PM > To: informix-list@iiug.org > Subject: > > Hello, > I am trying to create a trigger on table sysmaster:syssdblock. It > lets me create the trigger but it does not seem to working. > > The trigger is: > create trigger chk_sql_stmt insert on sysmaster:syssdblock > referencing new as new_sql > for each row (insert into "bbudba".sqlstmts values ( > new_sql.sdb_sessionid));> > The the priviledge to insert into 'bbudba'.sqlstmts is open to public and > the same with sysmaster:syssdblock but nothing gets put into the sqlstmts > table when a query is run. What am I missing? > > Thanks for any help. > > > > Keith A. Lewis > The Timken Company > lewis@timken.com > (330) 471-4119 > (330) 471-4034 (FAX) >

↪ replying to Lewis, Keith A.

cedarsiding@my-deja.com — Thu, 04 Jan 2001 01:43:57 GMT — source: Informix-list mailing list archive (1991-1998)

I'm a little surprised that the trigger creation was allowed in the first place. Certainly, the server can tell (if it wanted) that the target table is an SMI table. The SMI table is not really inserted into, so the insert trigger code path is never taken, and nothing happens. -cs Sent via Deja.com http://www.deja.com/