[jira] Updated: (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=all ] Knut Anders Hatlen updated DERBY-137: - Attachment: derby-137-v2.diff derby-137-v2.stat Thank you very much for reviewing, A B! You are right; NULLABLE, SEARCHABLE,

[jira] Updated: (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=all ] Knut Anders Hatlen updated DERBY-137: - Attachment: derby-137-v1.diff derby-137-v1.stat The attached patch changes the data types and adds missing columns so that the result

[jira] Updated: (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=all ] Knut Anders Hatlen updated DERBY-137: - Derby Info: [Patch Available] Patch is available and ready for review. Thanks! Derby metadata always returns JDBC 2 result sets, even when JDBC 3

[jira] Updated: (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=all ] Rick Hillegas updated DERBY-137: Priority: Critical (was: Major) Bumping the priority of this bug. Derby metadata always returns JDBC 2 result sets, even when JDBC 3 result sets are