Description
This exception occurs in the following case:
1. Create tables t1 and t2. Create a trigger on t2 whose triggering action is to insert a row into t1
2. Insert a value v1 into t2. Verify the trigger was fired by looking at contents of t1.
3. Drop table t1.
4. Insert a value v2 into t2. This will give an exception to indicate that table t1 does not exist.
5. Insert the same value v1 into t2. Instead of the exception in Step 4, this gives "ERROR XSAI2: The conglomerate (896) requested does not exist."
6. Re-create table t1.
7. Insert v2 into t2. This succeeds.
8. Try to insert the problem value v1 into t2. This still gives "ERROR XSAI2: The conglomerate (896) requested does not exist."
9. Shutdown and reconnect to the database. Try to insert the problem value v1 into t2. Now this succeeds.
So the exception occurs only in the specific case where we try to insert the same value that we had inserted before dropping the table referenced by the trigger. I'll attach a sql script to repro this.
Attachments
Attachments
Issue Links
- relates to
-
DERBY-1621 Trigger action statement is not recompile when there is a change that would affect it.
-
- Closed
-
-
-
- Closed
-