Date: Sat, 28 Feb 2009 17:06:39 +0100
On 27.02.2009 15:09, art_at_unsu.com wrote:
> On Feb 26, 4:55 pm, sybra..._at_hccnet.nl wrote:
>> On Thu, 26 Feb 2009 10:30:35 -0800 (PST), "a..._at_unsu.com" >> >> <ame..._at_iwc.net> wrote: >>> Well, the inserts into the table are done from procedures, functions >>> and packages. So, I'm not sure if your solution is what will work.
> I must say that I have tried it, along with about 10 others here.
You need to set values in all your procedures and read them in the trigger. Did you try that? You should also make sure that they are cleared once the trigger has read them so you do not accidentally reuse values from last time. But it seems that with this "hidden" transport of values the whole logic can become quite complex pretty soon. It would certainly be easier to add those additional values to the master table and have the trigger only copy them over.
If you use the idea I have blogge about recently you can also stuff them
into the temporary table. See
robert Received on Sat Feb 28 2009 - 10:06:39 CST