[jira] [Commented] (DERBY-5933) SQL sorting error

[ https://issues.apache.org/jira/browse/DERBY-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570103#comment-13570103 ] Dag H. Wanvik commented on DERBY-5933: -- I ran some trace on the lang suite, and it's

[jira] [Resolved] (DERBY-5933) SQL sorting error

[ https://issues.apache.org/jira/browse/DERBY-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik resolved DERBY-5933. -- Resolution: Fixed Fix Version/s: 10.10.0.0 SQL sorting error -

[jira] [Commented] (DERBY-5933) SQL sorting error

[ https://issues.apache.org/jira/browse/DERBY-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570106#comment-13570106 ] Dag H. Wanvik commented on DERBY-5933: -- Igor, feel free to close the issue if you

[Java DB - testing] Success nightly trunk (rev 1441923)

Java DB testing and reporting infrastructure. Success nightly trunk (rev 1441923) No errors or failures. Test report: http://download.java.net/javadesktop/derby/javadb-5571879-report/

[Java DB - testing] Failure continuous trunk (rev 1441869)

Java DB testing and reporting infrastructure. Failure continuous trunk (rev 1441869) 18 failures. Test report: http://download.java.net/javadesktop/derby/javadb-5571877-report/

[jira] [Commented] (DERBY-6065) LockTable API link in the documentation is broken

[ https://issues.apache.org/jira/browse/DERBY-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570265#comment-13570265 ] Rick Hillegas commented on DERBY-6065: -- I'm puzzled by this problem. When a user

[jira] [Commented] (DERBY-4921) Statement.executeUpdate(String sql, String[] columnNames) throws ERROR X0X0F.S exception with EmbeddedDriver

[ https://issues.apache.org/jira/browse/DERBY-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570302#comment-13570302 ] Philip Ogren commented on DERBY-4921: - If you change the client driver to behave as

[jira] [Commented] (DERBY-6065) LockTable API link in the documentation is broken

[ https://issues.apache.org/jira/browse/DERBY-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570319#comment-13570319 ] Kim Haase commented on DERBY-6065: -- The link to the javadoc was put in as part of the fix

[jira] [Assigned] (DERBY-6065) LockTable API link in the documentation is broken

[ https://issues.apache.org/jira/browse/DERBY-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Haase reassigned DERBY-6065: Assignee: Kim Haase LockTable API link in the documentation is broken

[jira] [Commented] (DERBY-6065) LockTable API link in the documentation is broken

[ https://issues.apache.org/jira/browse/DERBY-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570345#comment-13570345 ] Rick Hillegas commented on DERBY-6065: -- Hi Kim, I agree with this conclusion of

[jira] [Updated] (DERBY-6000) Implement support for JDBC 4.2

[ https://issues.apache.org/jira/browse/DERBY-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-6000: - Attachment: derby-6000-07-ab-batchUpdateException.diff Attaching

[jira] [Commented] (DERBY-5955) Prepare Derby to run with Compact Profiles (JEP 161)

[ https://issues.apache.org/jira/browse/DERBY-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570350#comment-13570350 ] Rick Hillegas commented on DERBY-5955: -- Thanks, Dag. These changes look good to me.

[jira] [Commented] (DERBY-6065) LockTable API link in the documentation is broken

[ https://issues.apache.org/jira/browse/DERBY-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570365#comment-13570365 ] Kim Haase commented on DERBY-6065: -- Way down at the bottom of the docs page are links to

[jira] [Commented] (DERBY-6065) LockTable API link in the documentation is broken

[ https://issues.apache.org/jira/browse/DERBY-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570381#comment-13570381 ] Rick Hillegas commented on DERBY-6065: -- Hi Kim, In general, the engine javadoc is

[jira] [Commented] (DERBY-6000) Implement support for JDBC 4.2

[ https://issues.apache.org/jira/browse/DERBY-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570429#comment-13570429 ] Rick Hillegas commented on DERBY-6000: -- Tests passed cleanly for me on

[jira] [Commented] (DERBY-6053) Client should use a prepared statement rather than regular statement for Connection.setTransactionIsolation

[ https://issues.apache.org/jira/browse/DERBY-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570499#comment-13570499 ] Kathey Marsden commented on DERBY-6053: --- Thanks Mamta for the patch. Do you get the

problem with dates on JavaDB - testing messages.

I thought I was not getting the testing messages sent to derby-dev. I just found that I have been getting them but they are all showing up as dated 12/31/1969 4pm in thunderbird. That was sorting them such that I was not seeing them. Not a big deal, just thought I would mention it if anyone

[jira] [Commented] (DERBY-6065) LockTable API link in the documentation is broken

[ https://issues.apache.org/jira/browse/DERBY-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570613#comment-13570613 ] Kim Haase commented on DERBY-6065: -- Yes, it might make sense to do for the LockTable API

[jira] [Commented] (DERBY-6061) Upgrade language is inconsistent

[ https://issues.apache.org/jira/browse/DERBY-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570660#comment-13570660 ] Kim Haase commented on DERBY-6061: -- I'm afraid I'm getting cold feet on this. We've been

[Java DB - testing] Failure continuous trunk (rev 1442195)

Java DB testing and reporting infrastructure. Failure continuous trunk (rev 1442195) 7 failures. Test report: http://download.java.net/javadesktop/derby/javadb-5571901-report/

[jira] [Commented] (DERBY-6053) Client should use a prepared statement rather than regular statement for Connection.setTransactionIsolation

[ https://issues.apache.org/jira/browse/DERBY-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570684#comment-13570684 ] Mamta A. Satoor commented on DERBY-6053: Hi Kathey, thanks for reviewing the

[jira] [Updated] (DERBY-6061) Upgrade language is inconsistent

[ https://issues.apache.org/jira/browse/DERBY-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Haase updated DERBY-6061: - Attachment: cdevcsecureroles.html DERBY-6061-code.diff DERBY-6061.diff

[jira] [Updated] (DERBY-6061) Upgrade language is inconsistent

[ https://issues.apache.org/jira/browse/DERBY-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Haase updated DERBY-6061: - Issue fix info: Patch Available Upgrade language is inconsistent

[jira] [Assigned] (DERBY-6053) Client should use a prepared statement rather than regular statement for Connection.setTransactionIsolation

[ https://issues.apache.org/jira/browse/DERBY-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor reassigned DERBY-6053: -- Assignee: Mamta A. Satoor Client should use a prepared statement rather than

[jira] [Created] (DERBY-6066) Client should use a prepared statement rather than regular statement for Connection.getTransactionIsolation

Mamta A. Satoor created DERBY-6066: -- Summary: Client should use a prepared statement rather than regular statement for Connection.getTransactionIsolation Key: DERBY-6066 URL:

[jira] [Commented] (DERBY-6061) Upgrade language is inconsistent

[ https://issues.apache.org/jira/browse/DERBY-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570715#comment-13570715 ] Mike Matrigali commented on DERBY-6061: --- i am wondering why you would remove the

[jira] [Commented] (DERBY-6061) Upgrade language is inconsistent

[ https://issues.apache.org/jira/browse/DERBY-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570909#comment-13570909 ] Dag H. Wanvik commented on DERBY-6061: -- I'm OK with keeping soft upgrade vs. (full)

[jira] [Commented] (DERBY-5546) ResultSet#updateBigDecimal on a REAL column does not do underflow checking

[ https://issues.apache.org/jira/browse/DERBY-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570917#comment-13570917 ] Dag H. Wanvik commented on DERBY-5546: -- Talked to Lance. We should follow the advice

[jira] [Commented] (DERBY-6053) Client should use a prepared statement rather than regular statement for Connection.setTransactionIsolation

[ https://issues.apache.org/jira/browse/DERBY-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571057#comment-13571057 ] Mamta A. Satoor commented on DERBY-6053: Committed changes into trunk(10.10.0.0

[jira] [Updated] (DERBY-6053) Client should use a prepared statement rather than regular statement for Connection.setTransactionIsolation

[ https://issues.apache.org/jira/browse/DERBY-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor updated DERBY-6053: --- Fix Version/s: 10.10.0.0 Client should use a prepared statement rather than regular

[jira] [Commented] (DERBY-6053) Client should use a prepared statement rather than regular statement for Connection.setTransactionIsolation

[ https://issues.apache.org/jira/browse/DERBY-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571060#comment-13571060 ] Mamta A. Satoor commented on DERBY-6053: I think the backport of the changes

[jira] [Commented] (DERBY-6045) in list multi-probe by primary key not chosen on tables with 256 rows

[ https://issues.apache.org/jira/browse/DERBY-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571092#comment-13571092 ] Mamta A. Satoor commented on DERBY-6045: BTW, I tried the little experiment I

[Java DB - testing] Success nightly trunk (rev 1442195)

Java DB testing and reporting infrastructure. Success nightly trunk (rev 1442195) No errors or failures. Test report: http://download.java.net/javadesktop/derby/javadb-5571911-report/

[jira] [Updated] (DERBY-6064) Failures in upgradeTests.Changes10_9 related to index cardinality statistics

[ https://issues.apache.org/jira/browse/DERBY-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-6064: --- Attachment: derby-6064-2a-fix_comment.diff Committed patch 2a, which improves the inaccurate