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
|Workflow||jira [ 12413268 ]||Default workflow, editable Closed status [ 12802575 ]|
|Issue & fix info||[High Value Fix]||[High Value Fix, Repro attached]|
|Issue & fix info||[High Value Fix]|
|Bug behavior facts||[High Value Fix]||[Regression]|
|Derby Categories||[High Value Fix]|
|Derby Info||[Patch Available, Regression]||[Regression]|
|Derby Info||[Regression]||[Patch Available, Regression]|
|Comment||[ Never mind the previous attachment and comment. I have attached this patch to the wrong issue. ]|
[ 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:
Fix for the collation bug.