Issue Details (XML | Word | Printable)

Key: DERBY-1435
Type: Bug Bug
Status: Closed Closed
Resolution: Duplicate
Priority: Major Major
Assignee: Yip Ng
Reporter: Deepa Remesh
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Derby

Conglomerate does not exist occurs in a specific case after dropping a table referenced by a trigger

Created: 22/Jun/06 06:41 AM   Updated: 13/Dec/07 09:04 AM
Return to search
Component/s: SQL
Affects Version/s: 10.2.1.6
Fix Version/s: 10.2.1.6

Time Tracking:
Not Specified

File Attachments:
  Size
File Licensed for inclusion in ASF works repro1435.sql 2006-06-22 07:00 AM Deepa Remesh 0.8 kB
File Licensed for inclusion in ASF works repro1435_for_functions.sql 2006-06-30 05:27 AM Deepa Remesh 0.8 kB
Issue Links:
Reference
 

Urgency: Normal
Resolution Date: 25/Aug/06 08:36 PM


 Description  « Hide
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.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no subversion log entries for this issue yet.