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 "Rick Hillegas (JIRA)" <ji...@apache.org> on 2007/07/31 21:53:53 UTC
[jira] Created: (DERBY-2983) The ResultSet returned by
DatabaseMetaData.getFunctions() does not contain a required column named
FUNCTION_TYPE.
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.2.0, 10.2.1.6, 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
Fix For: 10.4.0.0
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.
[jira] Commented: (DERBY-2983) The ResultSet returned by
DatabaseMetaData.getFunctions() does not contain a required column named
FUNCTION_TYPE.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516793 ]
Kathey Marsden commented on DERBY-2983:
---------------------------------------
I believe this is a dup of DERBY-2745
> 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
>
>
> 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.
[jira] Updated: (DERBY-2983) The ResultSet returned by
DatabaseMetaData.getFunctions() does not contain a required column named
FUNCTION_TYPE.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-2983:
---------------------------------
Derby Info: [Release Note Needed]
I believe that this issue needs a release note because we are inserting a new column in the middle of the old signature. I don't believe that this issue requires any upgrade logic. This is because the solution should not require adding any new system columns or procedures. See http://wiki.apache.org/db-derby/MetadataUpgrade
> 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
>
>
> 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.
[jira] Commented: (DERBY-2983) The ResultSet returned by
DatabaseMetaData.getFunctions() does not contain a required column named
FUNCTION_TYPE.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517587 ]
Rick Hillegas commented on DERBY-2983:
--------------------------------------
Just to be safe, I have attached a release note. This fix will affect users who are retrieving the result columns by position or who are handing the result set off to a generic data set reader and then relying on the current shape of the results.
> 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: 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.
[jira] Resolved: (DERBY-2983) The ResultSet returned by
DatabaseMetaData.getFunctions() does not contain a required column named
FUNCTION_TYPE.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden resolved DERBY-2983.
-----------------------------------
Resolution: Fixed
Derby Info: (was: [Release Note Needed])
This looks fixed in 10.4. Per Dan's comments a release note is probably not needed, since it is unlikely a user would be dependent on the wrong behavior.
If I am mistaken please reopen, remark Release Note Needed flag.
Kathey
> 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
> Components: JDBC
> Affects Versions: 10.2.1.6, 10.2.2.0, 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.
[jira] Commented: (DERBY-2983) The ResultSet returned by
DatabaseMetaData.getFunctions() does not contain a required column named
FUNCTION_TYPE.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517579 ]
Daniel John Debrunner commented on DERBY-2983:
----------------------------------------------
I don't think this strictly needs a release note. This method is only documented by the JDBC javadoc, not by Derby's documentation.
If the application was fetching columns by name then the application sees no change.
If the application was fetching the SPECIFIC_NAME column by number then they would have realized that there was a bug in Derby and reported it. Also since SPECIFIC_NAME is not supported in Derby means an application was unlikely to be using it.
> 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: 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.
[jira] Issue Comment Edited: (DERBY-2983) The ResultSet returned by
DatabaseMetaData.getFunctions() does not contain a required column named
FUNCTION_TYPE.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517618 ]
Rick Hillegas edited comment on DERBY-2983 at 8/3/07 1:01 PM:
--------------------------------------------------------------
Attaching derby-2983-01-newColumn.diff. This adds the FUNCTION_TYPE column to the ResultSet returned by DatabaseMetaData.getFunctions(). Touches the following files:
M java/engine/org/apache/derby/catalog/AliasInfo.java
M java/engine/org/apache/derby/catalog/types/SynonymAliasInfo.java
M java/engine/org/apache/derby/catalog/types/MethodAliasInfo.java
M java/engine/org/apache/derby/catalog/types/RoutineAliasInfo.java
Exposes a new method on AliasInfo. The method reports whether the Alias describes a TableFunction.
M java/engine/org/apache/derby/impl/jdbc/metadata.properties
Adds the new column to the query which materializes the ResultSet for DatabaseMetaData.getFunctions(). The query invokes the new method on AliasInfo and uses a CASE expression in order to determine what value to assign to the FUNCTION_TYPE column.
M java/shared/org/apache/derby/shared/common/reference/JDBC40Translation.java
M java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/JDBC40TranslationTest.java
Add the JDBC4 constants which are legal values for the new column.
M java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/TestDbMetaData.java
Update this unit test to account for the new column. Also verify that the columns returned by DatabaseMetaData.getFunctions() have the correct types.
was:
Attaching derby-2983-01-newColumn.diff. This adds the FUNCTION_TYPE column to the ResultSet returned by DatabaseMetaData.getFunctions(). Touches the following files:
M java/engine/org/apache/derby/catalog/AliasInfo.java
M java/engine/org/apache/derby/catalog/types/SynonymAliasInfo.java
M java/engine/org/apache/derby/catalog/types/MethodAliasInfo.java
M java/engine/org/apache/derby/catalog/types/RoutineAliasInfo.java
Exposes a new method on AliasInfo. The method reports whether the Alias describes a TableFunction.
M java/engine/org/apache/derby/impl/jdbc/metadata.properties
Adds the new column to the query which materializes the ResultSet for DatabaseMetaData.getFunctions(). The query invokes the new method on AliasInfo in order and uses a CASE expression to determine what value to assign to the FUNCTION_TYPE column.
M java/shared/org/apache/derby/shared/common/reference/JDBC40Translation.java
M java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/JDBC40TranslationTest.java
Add the JDBC4 constants which are legal values for the new column.
M java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/TestDbMetaData.java
Update this unit test to account for the new column. Also verify that the columns returned by DatabaseMetaData.getFunctions() have the correct types.
> 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.
[jira] Assigned: (DERBY-2983) The ResultSet returned by
DatabaseMetaData.getFunctions() does not contain a required column named
FUNCTION_TYPE.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas reassigned DERBY-2983:
------------------------------------
Assignee: Rick Hillegas
> 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
>
>
> 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.
[jira] Commented: (DERBY-2983) The ResultSet returned by
DatabaseMetaData.getFunctions() does not contain a required column named
FUNCTION_TYPE.
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559467#action_12559467 ]
Dyre Tjeldvoll commented on DERBY-2983:
---------------------------------------
Should this be resloved/closed?
> 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
> Components: JDBC
> Affects Versions: 10.2.1.6, 10.2.2.0, 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.
[jira] Updated: (DERBY-2983) The ResultSet returned by
DatabaseMetaData.getFunctions() does not contain a required column named
FUNCTION_TYPE.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel John Debrunner updated DERBY-2983:
-----------------------------------------
Component/s: JDBC
> 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
> Components: JDBC
> Affects Versions: 10.2.1.6, 10.2.2.0, 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.
[jira] Commented: (DERBY-2983) The ResultSet returned by
DatabaseMetaData.getFunctions() does not contain a required column named
FUNCTION_TYPE.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-2983) The ResultSet returned by
DatabaseMetaData.getFunctions() does not contain a required column named
FUNCTION_TYPE.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-2983:
---------------------------------
Attachment: derby-2983-01-newColumn.diff
Attaching derby-2983-01-newColumn.diff. This adds the FUNCTION_TYPE column to the ResultSet returned by DatabaseMetaData.getFunctions(). Touches the following files:
M java/engine/org/apache/derby/catalog/AliasInfo.java
M java/engine/org/apache/derby/catalog/types/SynonymAliasInfo.java
M java/engine/org/apache/derby/catalog/types/MethodAliasInfo.java
M java/engine/org/apache/derby/catalog/types/RoutineAliasInfo.java
Exposes a new method on AliasInfo. The method reports whether the Alias describes a TableFunction.
M java/engine/org/apache/derby/impl/jdbc/metadata.properties
Adds the new column to the query which materializes the ResultSet for DatabaseMetaData.getFunctions(). The query invokes the new method on AliasInfo in order and uses a CASE expression to determine what value to assign to the FUNCTION_TYPE column.
M java/shared/org/apache/derby/shared/common/reference/JDBC40Translation.java
M java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/JDBC40TranslationTest.java
Add the JDBC4 constants which are legal values for the new column.
M java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/TestDbMetaData.java
Update this unit test to account for the new column. Also verify that the columns returned by DatabaseMetaData.getFunctions() have the correct types.
> 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.
[jira] Updated: (DERBY-2983) The ResultSet returned by
DatabaseMetaData.getFunctions() does not contain a required column named
FUNCTION_TYPE.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-2983:
---------------------------------
Attachment: releaseNote.html
Attaching a release note for this issue.
> 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: 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.
[jira] Closed: (DERBY-2983) The ResultSet returned by
DatabaseMetaData.getFunctions() does not contain a required column named
FUNCTION_TYPE.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas closed DERBY-2983.
--------------------------------
> 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
> Components: JDBC
> Affects Versions: 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.4.1.3
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Fix For: 10.4.1.3
>
> 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.