NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
use Perl Log In
djberg96 (2603)
djberg96
(email not shown publicly)
(email not shown publicly)
Monday May 17, 2004
02:04 PM
More on insert triggers
For reasons that I cannot determine, the insert triggers no longer work. Oh, they compile fine, they LOOK like they should work but they just....don't. I get errors along the lines of, "attempting to insert a null value...", even though that's what the triggers are supposed to handle.
If I have to manually call sequence.nextval and insert it on my own, there's not much point to having the triggers. Besides, it'll improve performance.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
--Larry Wall in stab.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
some suggestions.. (Score:1)
I may be asking the obvious, but have you dropped and then recompiled ? On some heavily used/replicated/just plain weird databases, I've found that Oracle will assure you that the triggers/stored procedures/packages have compiled correctly when they haven't. I am sure there is a scientific reason for all this, but my cargo-cult means of dealing with it is embedding a couple of unmissable logging statements (in an autonomous transaction) and if that doesn't register on the log, just drop/recompile. In genera
Re:some suggestions.. (Score:2)
Yep, tried that first, but it still didn't seem to work, so I gave up. I just don't have time to futz with it. I think it's been a good work experience, though - avoid insert triggers. :)