db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1435) Conglomerate does not exist occurs in a specific case after dropping a table referenced by a trigger
Date Sat, 29 Jul 2006 01:50:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1435?page=comments#action_12424255 ] 
            
Daniel John Debrunner commented on DERBY-1435:
----------------------------------------------

I assume in the original description inserting the same value really means using the same
SQL statement, ie. inserting different values using the same statement with parameter markers
would cause the conglomerate not found exception.

> Conglomerate does not exist occurs in a specific case after dropping a table referenced
by a trigger
> ----------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1435
>                 URL: http://issues.apache.org/jira/browse/DERBY-1435
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.2.0.0
>            Reporter: Deepa Remesh
>         Attachments: repro1435.sql, repro1435_for_functions.sql
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message