[
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.
