Subject | action cancelled by trigger (255) to preserve data integrity |
---|---|
Author | tdtappe |
Post date | 2004-12-21T10:53:50Z |
(FB 1.0.3, error code -901, 335544342)
Does anybody know what exactly can cause this error?
Is there some description of the different kinds of
"integrity" triggers? What does 255 stand for?
BTW, I tried to do an update like:
UPDATE "MYTABLE" SET "COL1" = "TD$TMP1", "COL2" = "TD$TMP2", "COL3" =
"TD$TMP3", "COL4" = "TD$TMP4"
It is part of a "modify script" (modify type of columns) that is
executed by my own script-application.
After each dml statement a COMMIT is performed.
If I execute the above statement from my db admin tool, after the
script-app finished, I get NO ERROR !?
So I tried to re-execute the above statement from with my script-app,
after having disconnected and reconnected to the database.
But this doesn't seem to make any difference.
BTW, exactly the same application works without any problems with a FB
1.5 server / database.
--Heiko
Does anybody know what exactly can cause this error?
Is there some description of the different kinds of
"integrity" triggers? What does 255 stand for?
BTW, I tried to do an update like:
UPDATE "MYTABLE" SET "COL1" = "TD$TMP1", "COL2" = "TD$TMP2", "COL3" =
"TD$TMP3", "COL4" = "TD$TMP4"
It is part of a "modify script" (modify type of columns) that is
executed by my own script-application.
After each dml statement a COMMIT is performed.
If I execute the above statement from my db admin tool, after the
script-app finished, I get NO ERROR !?
So I tried to re-execute the above statement from with my script-app,
after having disconnected and reconnected to the database.
But this doesn't seem to make any difference.
BTW, exactly the same application works without any problems with a FB
1.5 server / database.
--Heiko