Disabling triggers.
Posted in 1999
Topics: Triggers, Constraints & Referential Integrity
We have a client using our software to monitor transactions on a database table. The operation goes: 1. Create temp. table. 2. Create Insert, Update and Delete triggers on the monitored table, to insert events into our temp. table about the transaction type and data used. 3. Poll the temporary table to see if it contains records. 4. For each record found, process the record, and delete it from the temporary table. 5. Sleep, then goto 3. The temporary table contains a column for each column in the monitored table, plus an additional transaction type column. The problem is that the triggers don't appear to be firing. My question is, is there a way of disabling triggers at the database and/or table level? I believe this may be what is happening. The supplier of the software that uses the database may have put this in for support reason's. BTW, The exact version of informix is unknown (customer has not said. I've asked, but info has not been forthcoming.) I know it is the SE version though. Sent via Deja.com http://www.deja.com/ Before you buy.
Yes triggers can be disabled at the table level. See the Guide to SQL Syntax manual. Art S. Kagel n9313324@my-deja.com wrote: > > We have a client using our software to monitor transactions on a > database table. > > The operation goes: > 1. Create temp. table. > 2. Create Insert, Update and Delete triggers on the monitored table, to > insert events into our temp. table about the transaction type and data > used. > 3. Poll the temporary table to see if it contains records. > 4. For each record found, process the record, and delete it from the > temporary table. > 5. Sleep, then goto 3. > > The temporary table contains a column for each column in the monitored > table, plus an additional transaction type column. > > The problem is that the triggers don't appear to be firing. > > My question is, is there a way of disabling triggers at the database > and/or table level? I believe this may be what is happening. The > supplier of the software that uses the database may have put this in for > support reason's. > > BTW, The exact version of informix is unknown (customer has not said. > I've asked, but info has not been forthcoming.) I know it is the SE > version though. > > Sent via Deja.com http://www.deja.com/ > Before you buy.
Is this the 'state' field in sysobjstate? We have verified that this is enabled at the table level, in this case. Is there a way of overiding this at the database level? In article <38304FA5.7CF93D37@bloomberg.net>, kagel@bloomberg.net wrote: > Yes triggers can be disabled at the table level. See the Guide to SQL > Syntax manual. > > Art S. Kagel > > n9313324@my-deja.com wrote: > > > > My question is, is there a way of disabling triggers at the database > > and/or table level? I believe this may be what is happening. The > > supplier of the software that uses the database may have put this in for > > support reason's. > > > > BTW, The exact version of informix is unknown (customer has not said. > > I've asked, but info has not been forthcoming.) I know it is the SE > > version though. Sent via Deja.com http://www.deja.com/ Before you buy.