Nope... :(
So, do you think that no database corruption can make this to happen?
I have two options here: the former... or I have a very hidden bug which I
didn't found yet which is deleting those missing records... just in case, I
created an "after delete" trigger to log any possible del
>>The table "sto_depositos" (it means warehouses) is populated entering all the
>>warehouses manually.
>>It barely changes.
Then when it is changing you can have situation like this?
Transaction 1 start
Transaction 2 start
Tranaction 1 change sto_depositos
Transaction 2 manipulate data and fir
Thanks Karol!!
The table "sto_depositos" (it means warehouses) is populated entering all the
warehouses manually. It barely changes. The "activo" field is used to hide some
warehouse I'm not longer using...
Sergio
Thanks for the answer!
> It depend how you table sto_depositos is populated and when you set activo=1?
The table is populated by this trigger, and the "activo" field doesn't change
(almost) ever!!! I'ts use only if I want to hide a warehouse that is not used
anymore...
Sergio.
Thanks!!!
> Have you checked if the trigger is still active, maybe it was disabled?
Yes I've checked it. The trigger is enabled and nobody disabled it before. I'm
the only one who changes such things...
> In the face of bugs or a corrupted database, of course anything is possible,
> but that
It depend how you table sto_depositos is populated and when you set activo=1?
Pozdrawiam,
Karol Bieniaszewski
Od: shg_siste...@yahoo.com.ar [firebird-support]
Wysłano: wtorek, 25 września 2018 16:49
Temat: [firebird-support] trigger not firing?
Hello! I use FB 2.5. I know that this its almos
On 25-9-2018 16:49, shg_siste...@yahoo.com.ar [firebird-support] wrote:
> Hello! I use FB 2.5. I know that this its almos imposible, but just in
> case I ask. Is there any chance that a trigger is not firing at all?
Have you checked if the trigger is still active, maybe it was disabled?
> I have
Hello! I use FB 2.5. Is there any chance that a trigger doesn't fire because a
database corruption? This is what seems to happen to my DB anyway...
I did a backup/restore and now the trigger works fine. Is it possible??
Both the backup and restore log files doesn't show any problem.
Se