[
https://issues.apache.org/jira/browse/DERBY-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493471
]
Rick Hillegas commented on DERBY-2587:
--------------------------------------
The patch looks good to me now but I'm afraid that it breaks the JUnit tests. I
have run the full JUnit tests twice against this patch and seen the following
error both times. As a reference, I ran the tests against a clean client
without the patch and I did not see this error:
There was 1 error:
1)
testTriggerNegative(org.apache.derbyTesting.functionTests.tests.lang.ProcedureInTriggerTest)java.sql.SQLException:
Operation 'CREATE TRIGGER' cannot be performed on object 'T1' because there is
an open ResultSet dependent on that object.
at
org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:95)
at
org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:346)
at org.apache.derby.client.am.Statement.execute(Statement.java:824)
at
org.apache.derbyTesting.functionTests.tests.lang.ProcedureInTriggerTest.testTriggerNegative(ProcedureInTriggerTest.java:406)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:88)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
Caused by: org.apache.derby.client.am.SqlException: Operation 'CREATE TRIGGER'
cannot be performed on object 'T1' because there is an open ResultSet dependent
on that object.
at
org.apache.derby.client.am.Statement.completeSqlca(Statement.java:1713)
at
org.apache.derby.client.am.Statement.completeExecuteImmediate(Statement.java:1322)
at
org.apache.derby.client.net.NetStatementReply.parseEXCSQLIMMreply(NetStatementReply.java:207)
at
org.apache.derby.client.net.NetStatementReply.readExecuteImmediate(NetStatementReply.java:58)
at
org.apache.derby.client.net.StatementReply.readExecuteImmediate(StatementReply.java:45)
at
org.apache.derby.client.net.NetStatement.readExecuteImmediate_(NetStatement.java:125)
at
org.apache.derby.client.am.Statement.readExecuteImmediate(Statement.java:1318)
at org.apache.derby.client.am.Statement.flowExecute(Statement.java:2014)
at org.apache.derby.client.am.Statement.executeX(Statement.java:829)
at org.apache.derby.client.am.Statement.execute(Statement.java:815)
... 37 more
FAILURES!!!
Tests run: 7521, Failures: 0, Errors: 1
> Connection.createClob() and Connection.createBlob() need to return locator
> support enabled LOB objects in the NetworkClient
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2587
> URL: https://issues.apache.org/jira/browse/DERBY-2587
> Project: Derby
> Issue Type: Sub-task
> Reporter: V.Narayanan
> Assigned To: V.Narayanan
> Attachments: ConnectionLocatorWork_v1.diff,
> ConnectionLocatorWork_v1.stat, ConnectionLocatorWork_v2.diff,
> ConnectionLocatorWork_v2.stat, ConnectionLocatorWork_v3.diff,
> ConnectionLocatorWork_v3.stat
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
