Subject | Re: [IBO] Unable to disable trigger with IBO Script |
---|---|
Author | Svein Erling Tysvær |
Post date | 2001-07-02T10:30:42Z |
Hi Augey, sorry for the late reply, but I don't work weekends.
missing something. Does this mean that you have a trigger that inserts a
generated value at every insert? The IBO way of doing it, is to check if
the field contains a null value and only call the generator if that's the
case (this makes it possible for GeneratorLinks to work even if there is a
trigger). Then you don't have to worry about disabling/enabling your
trigger at all.
Enabling/disabling a trigger is DDL (I think), which you ought to be a bit
careful with in a running program. It should work fine the first 255 times
(unless some other users try to insert normally when you run your script),
but then you need to do a backup/restore for it to be reset.
Set
>I have a small SQL script to insert a bunch of things into a databaseI get suspicious when I read something like this, and I think you may be
>with a trigger that I use to keep a unique key for each value.
>However, when I put that working script into IB_Script it works fine
>but the trigger is never disabled (so the key has a funkey number from
>the generator)
>Is there something I am missing?
missing something. Does this mean that you have a trigger that inserts a
generated value at every insert? The IBO way of doing it, is to check if
the field contains a null value and only call the generator if that's the
case (this makes it possible for GeneratorLinks to work even if there is a
trigger). Then you don't have to worry about disabling/enabling your
trigger at all.
Enabling/disabling a trigger is DDL (I think), which you ought to be a bit
careful with in a running program. It should work fine the first 255 times
(unless some other users try to insert normally when you run your script),
but then you need to do a backup/restore for it to be reset.
Set