[jira] Commented: (DERBY-137) Derby metadata always returns JDBC 2 result sets, even when JDBC 3 result sets are required.

[ http://issues.apache.org/jira/browse/DERBY-137?page=comments#action_12418050 ] A B commented on DERBY-137: --- Derbyall (including the upgrade test) still passes. Do you think these changes are OK? Yes, the latest patch looks good to me. Thanks much for

[jira] Commented: (DERBY-137) Derby metadata always returns JDBC 2 result sets, even when JDBC 3 result sets are required.

[ http://issues.apache.org/jira/browse/DERBY-137?page=comments#action_12417738 ] Knut Anders Hatlen commented on DERBY-137: -- I plan to commit this patch tomorrow. If someone is planning to review, please let me know and I'll hold the commit.

[jira] Commented: (DERBY-137) Derby metadata always returns JDBC 2 result sets, even when JDBC 3 result sets are required.

[ http://issues.apache.org/jira/browse/DERBY-137?page=comments#action_12417835 ] A B commented on DERBY-137: --- I hope to review these changes today (06/26 PST) and will post comments as appropriate. Thanks for your patience... Derby metadata always returns

[jira] Commented: (DERBY-137) Derby metadata always returns JDBC 2 result sets, even when JDBC 3 result sets are required.

[ http://issues.apache.org/jira/browse/DERBY-137?page=comments#action_12416518 ] Knut Anders Hatlen commented on DERBY-137: -- I have (or more precisely, a test program of mine has) gone through all the DatabaseMetaData methods and compared them to