[ https://issues.apache.org/jira/browse/DERBY-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041645#comment-13041645 ]
Dag H. Wanvik commented on DERBY-5237: -------------------------------------- Jim, I have committed a fix for this to the the trunk and the 10.8 maintenance branches. Would you be willing to test a modified 10.8 bundle (not for production!) to see if it solves your problem? If you can't build it yourself, you could get the jars from me. > 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 > 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. For more information on JIRA, see: http://www.atlassian.com/software/jira