You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mike Matrigali (Updated) (JIRA)" <ji...@apache.org> on 2012/02/16 21:45:00 UTC
[jira] [Updated] (DERBY-5237) interrupting thread performing
"create table" doesn't cause SQLException with sql state "08000"
[ https://issues.apache.org/jira/browse/DERBY-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-5237:
----------------------------------
Component/s: SQL
> interrupting thread performing "create table" doesn't cause SQLException with sql state "08000"
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-5237
> URL: https://issues.apache.org/jira/browse/DERBY-5237
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.8.1.2
> Environment: Windows 7, JDK 1.6.0_25
> Reporter: Jim Newsham
> Attachments: DerbyInterruptTest.java
>
>
> We would like to take advantage of the recent Derby enhancement for handling thread interruption. http://db.apache.org/derby/docs/dev/devguide/devguide-single.html, section "Working with database threads in an embedded environment" states that in the case of exception, the calling code should receive a SQLException with code 08000. In my testing, this appears to work for sql "insert" statements, but not for sql "create table" statements. This is an issue for us since database tables are created dynamically over the course of the application's normal operation.
> Junit test repro to follow.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira