Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Thomas Kudrass — — source: Informix-list mailing list archive (1991-1998)
Hallo everywhere,
I'm looking for a good way to prohibit certain operations, e.g. I don't want
that a table is manipulated by an UPDATE statement. But the triggers (available
since version 5.0.1) don't allow me to rollback a SQL statement, because the
transaction concept is only available in the embedding SQL programming linke ESQL/C.
When using the BEFORE clause of the Trigger the triggering action (e.g. my bad update) has already occured, this is not desirable.
Any ideas from the Informix community ?
---
Thomas Kudrass
kudrass@dvs1.informatik.th-darmstadt.de
Your privacy choices
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.