[
https://issues.apache.org/jira/browse/DERBY-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-3083:
---------------------------------
Attachment: derby-716-10-datatypesCollation-aa.diff
Attaching derby-716-10-datatypesCollation-aa.diff. This adds tests verifying
the following:
1) Make sure that Derby calls the expected getXXX() method for each legal
datatype in the rowset returned by a table function.
2) Make sure that string columns in the returned rowset have the expected
collation (described in the previous comment).
The second test uncovered a bug: we were always applying BASIC collation to
string columns in the returned rowsets. This patch fixes that bug.
Touches the following files:
M java/engine/org/apache/derby/impl/sql/compile/CreateAliasNode.java
M java/engine/org/apache/derby/catalog/types/TypeDescriptorImpl.java
Fix for the collation bug.
M
java/testing/org/apache/derbyTesting/functionTests/tests/lang/TableFunctionTest.java
M
java/testing/org/apache/derbyTesting/functionTests/tests/lang/StringArrayVTI.java
New tests.
> Network server demands a file called "derbynet.jar" in classpath
> ----------------------------------------------------------------
>
> Key: DERBY-3083
> URL: https://issues.apache.org/jira/browse/DERBY-3083
> Project: Derby
> Issue Type: Bug
> Components: Tools
> Affects Versions: 10.3.1.4
> Reporter: Aaron Digulla
> Attachments: derby-716-10-datatypesCollation-aa.diff
>
>
> The network server will not start if the derbynet jar is added under a
> different name than "derbynet.jar" to the classpath. This makes it impossible
> to use it in maven projects where the jar is renamed to
> "derbynet-10.3.1.4.jar".
> This did work with 10.2.2.0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
