Trigger On Insert - Please Help
Posted in 1999
Topics: Stored Procedures & SPL, Triggers, Constraints & Referential Integrity
Can anybody help me with an issue with triggers on IDS. We have a third party application that inserts values into a table - we have no control over what happens here. We then need to update one column of the record based upon other details within the record. If we have an insert trigger that calls a stored procedure which updates the table (directly or indirectly through views, synonyms, other procedures, other triggers etc) then we get the error "747: Table or column matches object referenced in triggering statement.". I understand why we get this but what I need is a way around this. This MUST be a common requirement and can be overcome in other database vendor products but NOT Informix from what I can tell. Any ideas?? PS : Will Informix ever produce a SP language to rival Oracle PL/SQL or MS Transact - if they did it would be the perfect database server for everyone (including developers and third party product authors). --== Sent via Deja.com http://www.deja.com/ ==-- ---Share what you know. Learn what you don't.---
Hi Jeff, There is a new tool - SPL Workstation. It features interactive debugger for stored procedures and triggers that allows execute SPL line-by-line, set breakpoints, watch and modify variable values, step into nested procedures and more. It also has integrated color-coded SQL Editor optimized to write stored procedures and triggers, Object Explorer, Object Dependencies Analyzer that works for both SPL and SQL objects, Data Editor. SPL Workstation makes it much easier to develop, debug and analyze server-side applications. You can download an evaluation version from: www.agsltd.com Hope it helps, Regards, Arkady Jeff McFee wrote in message <7hh376$ci$1@nnrp1.deja.com>... >Can anybody help me with an issue with triggers on IDS. > >We have a third party application that inserts values into a table - we >have no control over what happens here. We then need to update one >column of the record based upon other details within the record. > >If we have an insert trigger that calls a stored procedure which >updates the table (directly or indirectly through views, synonyms, >other procedures, other triggers etc) then we get the error "747: Table >or column matches object referenced in triggering statement.". I >understand why we get this but what I need is a way around this. > >This MUST be a common requirement and can be overcome in other database >vendor products but NOT Informix from what I can tell. Any ideas?? > >PS : Will Informix ever produce a SP language to rival Oracle PL/SQL or >MS Transact - if they did it would be the perfect database server for >everyone (including developers and third party product authors). > > >--== Sent via Deja.com http://www.deja.com/ ==-- >---Share what you know. Learn what you don't.---