[
https://issues.apache.org/jira/browse/DERBY-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-4479.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.6.0.0
Thanks Dag and Knut for the reviews and assistance. Committed to the trunk as
revision 909176.
Knut, I think your observation about the usefulness of caching DDL statements
that
are very unlikely to be re-issued is quite valid, and I think it would be a good
enhancement to pursue in the future. My current itch was to resolve the NPE, so
I decided this this change was reasonable and straightforward and a good
incremental
improvement and so I committed it.
I think it would be great if somebody took some time to take a deeper and more
system-wide look at the overall operation of the statement cache mechanism, but
I'm afraid I don't have the time to do that right now so I'm marking this issue
as resolved.
> after rename table a to b then create table a statement execute cause null
> point exception
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-4479
> URL: https://issues.apache.org/jira/browse/DERBY-4479
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.0.2.1, 10.1.1.0, 10.2.2.0, 10.3.3.0, 10.4.2.0,
> 10.5.3.0, 10.6.0.0
> Environment: Windows XP SP2
> java version "1.5.0_16"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b02)
> Java HotSpot(TM) Client VM (build 1.5.0_16-b02, mixed mode, sharing)
> Reporter: dragon lee
> Assignee: Bryan Pendleton
> Priority: Minor
> Fix For: 10.6.0.0
>
> Attachments: patch.diff
>
>
> step 1 : create original table
> CREATE TABLE BPEL_ARCHIVE (
> EVENT_TIME CHAR(17) NOT NULL,
> BUSINESS_ID VARCHAR(100) NOT NULL,
> EVENT_TYPE INT,
> EVENT_CONTENT BLOB,
> PRIMARY KEY ( EVENT_TIME )
> )
> step 2 : rename original table to backup table
> RENAME TABLE BPEL_ARCHIVE TO
> BPEL_ARCHIVE_200912171148_200912171148
> step 3 : create original table
> cause error...
> java.sql.SQLException: Java exception: ': java.lang.NullPointerException'.
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
> at
> org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown
> Source)
> at
> world.dragon.service.bpel.event.derby.DerbyArchiveEndpoint.switchTargetTable(DerbyArchiveEndpoint.java:295)
> ...................................
> Caused by: java.lang.NullPointerException
> at
> org.apache.derby.impl.sql.execute.CreateIndexConstantAction.executeConstantAction(Unknown
> Source)
> at
> org.apache.derby.impl.sql.execute.CreateConstraintConstantAction.executeConstantAction(Unknown
> Source)
> at
> org.apache.derby.impl.sql.execute.CreateTableConstantAction.executeConstantAction(Unknown
> Source)
> at org.apache.derby.impl.sql.execute.MiscResultSet.open(Unknown Source)
> at
> org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(Unknown Source)
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown
> Source)
> ... 28 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
