Saurabh Vyas (JIRA) wrote:
[ https://issues.apache.org/jira/browse/DERBY-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466953 ]
Saurabh Vyas commented on DERBY-2244:
-------------------------------------
This issue is addressed by the patch for DERBY-2243
(https://issues.apache.org/jira/browse/DERBY-2243) and that is now committed.
So should I link this to Derby-2243 or else changed the status directly to
resolved ?
Hi Saurabh,
My take on this, is that you should link to DERBY-2243 (and add a
comment, but you already have one) and then mark DERBY-2244 as fixed,
because the bug has been corrected by the other issue.
It should also be closed when you/reporter has verified it. The
fixed/close steps can be combined, saves one mail message :)
I don't know why DERBY-2243 is not marked as fixed. Is there more work
to be done on it?
--
Kristian
DatabaseMetaData.supportsExpressionsInOrderBy() returns false
-------------------------------------------------------------
Key: DERBY-2244
URL: https://issues.apache.org/jira/browse/DERBY-2244
Project: Derby
Issue Type: Bug
Components: JDBC
Affects Versions: 10.2.1.6, 10.2.2.0, 10.3.0.0
Reporter: Daniel John Debrunner
Assigned To: Saurabh Vyas
Priority: Minor
Expressions in the ORDER BY clause were added by DERBY-134
