db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2983) The ResultSet returned by DatabaseMetaData.getFunctions() does not contain a required column named FUNCTION_TYPE.
Date Mon, 06 Aug 2007 15:43:59 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517969
] 

Rick Hillegas commented on DERBY-2983:
--------------------------------------

Committed derby-2983-01-newColumn.diff at subversion revision 563172. The regression tests
ran cleanly for me on jdk1.4. The tests also ran cleanly under Java 6 except for the following
two problems in ProcedureInTriggerTest. I reran that test by itself a couple times and could
not reproduce the 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.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:95)
	at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Util.java:202)
	at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(TransactionResourceImpl.java:391)
	at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(TransactionResourceImpl.java:346)
	at org.apache.derby.impl.jdbc.EmbedConnection.handleException(EmbedConnection.java:1572)
	at org.apache.derby.impl.jdbc.ConnectionChild.handleException(ConnectionChild.java:81)
	at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1293)
	at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:596)
	at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:528)
	at org.apache.derbyTesting.functionTests.tests.lang.ProcedureInTriggerTest.testTriggerNegative(ProcedureInTriggerTest.java:394)
	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:95)
	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 org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
Caused by: 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.impl.jdbc.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:45)
	at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(SQLExceptionFactory40.java:135)
	at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:70)
	... 38 more
Caused by: ERROR X0X95: Operation 'CREATE TRIGGER' cannot be performed on object 'T1' because
there is an open ResultSet dependent on that object.
	at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:301)
	at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.verifyNoOpenResultSets(GenericLanguageConnectionContext.java:1749)
	at org.apache.derby.impl.sql.GenericPreparedStatement.prepareToInvalidate(GenericPreparedStatement.java:694)
	at org.apache.derby.impl.sql.depend.BasicDependencyManager.coreInvalidateFor(BasicDependencyManager.java:382)
	at org.apache.derby.impl.sql.depend.BasicDependencyManager.invalidateFor(BasicDependencyManager.java:241)
	at org.apache.derby.impl.sql.execute.CreateTriggerConstantAction.executeConstantAction(CreateTriggerConstantAction.java:275)
	at org.apache.derby.impl.sql.execute.MiscResultSet.open(MiscResultSet.java:64)
	at org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java:370)
	at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1203)
	... 32 more
2) 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:362)
	at org.apache.derby.client.am.Statement.execute(Statement.java:819)
	at org.apache.derbyTesting.functionTests.tests.lang.ProcedureInTriggerTest.testTriggerNegative(ProcedureInTriggerTest.java:394)
	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:95)
	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 org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
	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 org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
	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:1708)
	at org.apache.derby.client.am.Statement.completeExecuteImmediate(Statement.java:1317)
	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:1313)
	at org.apache.derby.client.am.Statement.flowExecute(Statement.java:2009)
	at org.apache.derby.client.am.Statement.executeX(Statement.java:824)
	at org.apache.derby.client.am.Statement.execute(Statement.java:810)
	... 39 more

FAILURES!!!
Tests run: 9151,  Failures: 0,  Errors: 2


> The ResultSet returned by DatabaseMetaData.getFunctions() does not contain a required
column named FUNCTION_TYPE.
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2983
>                 URL: https://issues.apache.org/jira/browse/DERBY-2983
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.2.1.6, 10.2.2.0, 10.3.0.0, 10.3.1.0, 10.3.1.1, 10.3.1.2, 10.3.1.3,
10.3.1.4, 10.4.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>             Fix For: 10.4.0.0
>
>         Attachments: derby-2983-01-newColumn.diff, releaseNote.html
>
>
> The FUNCTION_TYPE column, sandwiched between REMARKS and SPECIFIC_NAME, is supposed to
describe the return type of the function.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message