[jira] [Resolved] (DERBY-4160) getMetaData().getIndexInfo crashes with "ERROR X0Y68: Column 'PARAM1' already exists."

[ https://issues.apache.org/jira/browse/DERBY-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen resolved DERBY-4160. --- Resolution: Fixed Fix Version/s: 10.10.1.4 > getMetaData().getIndexInfo crashe

[jira] [Updated] (DERBY-6493) Improve reporting of exceptions wrapped in InvocationTargetException

[ https://issues.apache.org/jira/browse/DERBY-6493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-6493: -- Labels: backport_reject_10_10 (was: ) Thanks, Dag. I agree that it shouldn't be backpo

[jira] [Commented] (DERBY-6493) Improve reporting of exceptions wrapped in InvocationTargetException

[ https://issues.apache.org/jira/browse/DERBY-6493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920739#comment-13920739 ] ASF subversion and git services commented on DERBY-6493: Commit 15

[jira] [Resolved] (DERBY-6493) Improve reporting of exceptions wrapped in InvocationTargetException

[ https://issues.apache.org/jira/browse/DERBY-6493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen resolved DERBY-6493. --- Resolution: Fixed Fix Version/s: 10.11.0.0 Issue & fix info: (was:

[jira] [Comment Edited] (DERBY-6374) Bulk insert of data with nullable UNIQUE constraint fails to detect duplicates

[ https://issues.apache.org/jira/browse/DERBY-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919681#comment-13919681 ] Dag H. Wanvik edited comment on DERBY-6374 at 3/5/14 12:16 PM: -

[jira] [Commented] (DERBY-6408) EXISTS returns NULL instead of FALSE

[ https://issues.apache.org/jira/browse/DERBY-6408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920815#comment-13920815 ] ASF subversion and git services commented on DERBY-6408: Commit 15

[jira] [Created] (DERBY-6495) Error in SelectivityTest.testBasic

Rick Hillegas created DERBY-6495: Summary: Error in SelectivityTest.testBasic Key: DERBY-6495 URL: https://issues.apache.org/jira/browse/DERBY-6495 Project: Derby Issue Type: Bug Co

[jira] [Resolved] (DERBY-6378) OFFSET/FETCH NEXT ignored when query is enclosed in parentheses

[ https://issues.apache.org/jira/browse/DERBY-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik resolved DERBY-6378. -- Resolution: Fixed Fix Version/s: 10.11.0.0 > OFFSET/FETCH NEXT ignored when query is enc

[jira] [Updated] (DERBY-6378) OFFSET/FETCH NEXT ignored when query is enclosed in parentheses

[ https://issues.apache.org/jira/browse/DERBY-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik updated DERBY-6378: - Issue & fix info: Repro attached (was: Patch Available,Repro attached) > OFFSET/FETCH NEXT ignor

[jira] [Commented] (DERBY-6025) Wrong results with IN lists and indexes in territory based collation

[ https://issues.apache.org/jira/browse/DERBY-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920857#comment-13920857 ] Knut Anders Hatlen commented on DERBY-6025: --- Thanks for fixing this bug, Mamta.

[jira] [Updated] (DERBY-3155) Support for SQL:2003 MERGE statement

[ https://issues.apache.org/jira/browse/DERBY-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3155: - Attachment: derby-3155-34-aa-updatePrivs.diff Attaching derby-3155-34-aa-updatePrivs.diff. This p

[jira] [Commented] (DERBY-6408) EXISTS returns NULL instead of FALSE

[ https://issues.apache.org/jira/browse/DERBY-6408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920888#comment-13920888 ] ASF subversion and git services commented on DERBY-6408: Commit 15

[jira] [Updated] (DERBY-6408) EXISTS returns NULL instead of FALSE

[ https://issues.apache.org/jira/browse/DERBY-6408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-6408: -- Fix Version/s: 10.10.1.4 > EXISTS returns NULL instead of FALSE > -

[jira] [Commented] (DERBY-6409) Wrong result from quantified comparison

[ https://issues.apache.org/jira/browse/DERBY-6409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920889#comment-13920889 ] ASF subversion and git services commented on DERBY-6409: Commit 15

[jira] [Commented] (DERBY-6025) Wrong results with IN lists and indexes in territory based collation

[ https://issues.apache.org/jira/browse/DERBY-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921017#comment-13921017 ] ASF subversion and git services commented on DERBY-6025: Commit 15

[jira] [Updated] (DERBY-3155) Support for SQL:2003 MERGE statement

[ https://issues.apache.org/jira/browse/DERBY-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3155: - Attachment: derby-3155-34-ab-updatePrivs.diff Attaching derby-3155-34-ab-updatePrivs.diff. The pr

[jira] [Updated] (DERBY-6025) Wrong results with IN lists and indexes in territory based collation

[ https://issues.apache.org/jira/browse/DERBY-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor updated DERBY-6025: --- Fix Version/s: 10.11.0.0 > Wrong results with IN lists and indexes in territory based collati

[jira] [Commented] (DERBY-6025) Wrong results with IN lists and indexes in territory based collation

[ https://issues.apache.org/jira/browse/DERBY-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921025#comment-13921025 ] Mamta A. Satoor commented on DERBY-6025: Thanks for reviewing the patch Knut. It i

[jira] [Commented] (DERBY-3155) Support for SQL:2003 MERGE statement

[ https://issues.apache.org/jira/browse/DERBY-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921026#comment-13921026 ] ASF subversion and git services commented on DERBY-3155: Commit 15

[jira] [Commented] (DERBY-896) Cast date to timestamp results in "ERROR 42846: Cannot convert types 'DATE' to 'TIMESTAMP'."

[ https://issues.apache.org/jira/browse/DERBY-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921203#comment-13921203 ] ASF subversion and git services commented on DERBY-896: --- Commit 15746

[jira] [Assigned] (DERBY-6495) Error in SelectivityTest.testBasic

[ https://issues.apache.org/jira/browse/DERBY-6495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrna van Lunteren reassigned DERBY-6495: - Assignee: Myrna van Lunteren > Error in SelectivityTest.testBasic > -

[jira] [Commented] (DERBY-6495) Error in SelectivityTest.testBasic

[ https://issues.apache.org/jira/browse/DERBY-6495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921213#comment-13921213 ] Myrna van Lunteren commented on DERBY-6495: --- Looks like sort order is not comple

[jira] [Updated] (DERBY-6495) Error in SelectivityTest.testBasic

[ https://issues.apache.org/jira/browse/DERBY-6495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrna van Lunteren updated DERBY-6495: -- Attachment: DERBY-6495.diff This patch addresses a number of selects in the decorateSQL

[jira] [Created] (DERBY-6496) Optional tool registration may fail because the CompilerContext is not always available at execution time.

Rick Hillegas created DERBY-6496: Summary: Optional tool registration may fail because the CompilerContext is not always available at execution time. Key: DERBY-6496 URL: https://issues.apache.org/jira/browse/DERB

[jira] [Commented] (DERBY-6495) Error in SelectivityTest.testBasic

[ https://issues.apache.org/jira/browse/DERBY-6495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921260#comment-13921260 ] ASF subversion and git services commented on DERBY-6495: Commit 15

[jira] [Assigned] (DERBY-6496) Optional tool registration may fail because the CompilerContext is not always available at execution time.

[ https://issues.apache.org/jira/browse/DERBY-6496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas reassigned DERBY-6496: Assignee: Rick Hillegas > Optional tool registration may fail because the CompilerContext i

[jira] [Resolved] (DERBY-6216) XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open

[ https://issues.apache.org/jira/browse/DERBY-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrna van Lunteren resolved DERBY-6216. --- Resolution: Fixed Fix Version/s: 10.10.1.4 Assignee: Bryan Pendleton

[jira] [Updated] (DERBY-6496) Optional tool registration may fail because the CompilerContext is not always available at execution time.

[ https://issues.apache.org/jira/browse/DERBY-6496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-6496: - Attachment: derby-6496-01-aa-useClassFactoryContext.diff Attaching derby-6496-01-aa-useClassFacto

[jira] [Commented] (DERBY-6492) ASSERT FAILED: LanguageConnectionContext is null

[ https://issues.apache.org/jira/browse/DERBY-6492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921289#comment-13921289 ] Rick Hillegas commented on DERBY-6492: -- Linking this issue to DERBY-6496. It may be a

[jira] [Commented] (DERBY-6496) Optional tool registration may fail because the CompilerContext is not always available at execution time.

[ https://issues.apache.org/jira/browse/DERBY-6496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921335#comment-13921335 ] Knut Anders Hatlen commented on DERBY-6496: --- This might be the same bug as DERBY

[jira] [Resolved] (DERBY-6495) Error in SelectivityTest.testBasic

[ https://issues.apache.org/jira/browse/DERBY-6495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrna van Lunteren resolved DERBY-6495. --- Resolution: Fixed Fix Version/s: 10.11.0.0 > Error in SelectivityTest.testBasi

[jira] [Commented] (DERBY-6495) Error in SelectivityTest.testBasic

[ https://issues.apache.org/jira/browse/DERBY-6495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921349#comment-13921349 ] Myrna van Lunteren commented on DERBY-6495: --- Linking to DERBY-3955 - the failure

[jira] [Created] (DERBY-6497) Deadlock with OnDelete="CASCADE"

Billow Gao created DERBY-6497: - Summary: Deadlock with OnDelete="CASCADE" Key: DERBY-6497 URL: https://issues.apache.org/jira/browse/DERBY-6497 Project: Derby Issue Type: Bug Components

[jira] [Updated] (DERBY-6496) Optional tool registration may fail because the CompilerContext is not always available at execution time.

[ https://issues.apache.org/jira/browse/DERBY-6496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-6496: - Attachment: derby-6496-01-ab-useClassFactoryContext.diff Attaching a second rev of the patch, de

[jira] [Commented] (DERBY-6491) SELECT statements incorrectly require USAGE privilege on column types

[ https://issues.apache.org/jira/browse/DERBY-6491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921462#comment-13921462 ] Mamta A. Satoor commented on DERBY-6491: Rick, should those items be handled in a

[jira] [Commented] (DERBY-6461) DatabaseMetaData.getExportedKeys() and getImportedKeys() incorrectly return information on UNIQUE constraints

[ https://issues.apache.org/jira/browse/DERBY-6461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921495#comment-13921495 ] Myrna van Lunteren commented on DERBY-6461: --- There's no fix for this yet, but ju

[jira] [Updated] (DERBY-6214) PreparedStatement.setObject(int, Object, Types.CLOB) fail with DerbyNet

[ https://issues.apache.org/jira/browse/DERBY-6214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor updated DERBY-6214: --- Assignee: (was: Mamta A. Satoor) > PreparedStatement.setObject(int, Object, Types.CLOB) f

[jira] [Commented] (DERBY-6214) PreparedStatement.setObject(int, Object, Types.CLOB) fail with DerbyNet

[ https://issues.apache.org/jira/browse/DERBY-6214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921501#comment-13921501 ] Mamta A. Satoor commented on DERBY-6214: Not working on this currently > Prepared

[jira] [Updated] (DERBY-5313) Assert failure with CASE expression in GROUP BY clause

[ https://issues.apache.org/jira/browse/DERBY-5313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-5313: -- Affects Version/s: 10.4.2.1 > Assert failure with CASE expression in GROUP BY clause >

[jira] [Commented] (DERBY-6256) Move the XmlVTI into the product.

[ https://issues.apache.org/jira/browse/DERBY-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921558#comment-13921558 ] Myrna van Lunteren commented on DERBY-6256: --- Looks like fixes have gone in, will

[jira] [Created] (DERBY-6498) Derby does not always automatically create a user's schema

Myrna van Lunteren created DERBY-6498: - Summary: Derby does not always automatically create a user's schema Key: DERBY-6498 URL: https://issues.apache.org/jira/browse/DERBY-6498 Project: Derby

[jira] [Commented] (DERBY-6498) Derby does not always automatically create a user's schema

[ https://issues.apache.org/jira/browse/DERBY-6498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921682#comment-13921682 ] Myrna van Lunteren commented on DERBY-6498: --- In DERBY-6361 Rick said we needed:

[jira] [Commented] (DERBY-6361) Valid statements rejected if Derby has not implicitly created the current user's schema.

[ https://issues.apache.org/jira/browse/DERBY-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921683#comment-13921683 ] Myrna van Lunteren commented on DERBY-6361: --- I understand your concern Rick. But

[jira] [Resolved] (DERBY-6361) Valid statements rejected if Derby has not implicitly created the current user's schema.

[ https://issues.apache.org/jira/browse/DERBY-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrna van Lunteren resolved DERBY-6361. --- Resolution: Fixed Fix Version/s: 10.11.0.0 > Valid statements rejected if Derb

[jira] [Updated] (DERBY-6250) nightly regression test failure: jdbc4.LoginTimeoutTest testBasic client/server java.sql.SQLTimeoutException: XBDA0, Login timeout Exceeded and junit.framework.AssertionF

[ https://issues.apache.org/jira/browse/DERBY-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrna van Lunteren updated DERBY-6250: -- Attachment: DERBY-6250.diff Attaching a patch which - adds some more data to the error

[jira] [Updated] (DERBY-6250) nightly regression test failure: jdbc4.LoginTimeoutTest testBasic client/server java.sql.SQLTimeoutException: XBDA0, Login timeout Exceeded and junit.framework.AssertionF

[ https://issues.apache.org/jira/browse/DERBY-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrna van Lunteren updated DERBY-6250: -- Issue & fix info: Patch Available > nightly regression test failure: jdbc4.LoginTimeout

[jira] [Commented] (DERBY-6496) Optional tool registration may fail because the CompilerContext is not always available at execution time.

[ https://issues.apache.org/jira/browse/DERBY-6496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921917#comment-13921917 ] ASF subversion and git services commented on DERBY-6496: Commit 15

[jira] [Commented] (DERBY-6491) SELECT statements incorrectly require USAGE privilege on column types

[ https://issues.apache.org/jira/browse/DERBY-6491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921927#comment-13921927 ] Rick Hillegas commented on DERBY-6491: -- Hi Mamta, Yes, I agree that overhauling UDT

[jira] [Resolved] (DERBY-6482) Revamp the vti demo to look and behave more like the other demos.

[ https://issues.apache.org/jira/browse/DERBY-6482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas resolved DERBY-6482. -- Resolution: Fixed Looks like we're done with this issue. > Revamp the vti demo to look and beh

[jira] [Resolved] (DERBY-6256) Move the XmlVTI into the product.

[ https://issues.apache.org/jira/browse/DERBY-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas resolved DERBY-6256. -- Resolution: Fixed Thanks for that nudge, Myrna. Resolving this issue. > Move the XmlVTI into t

[Java DB - testing] Failure nightly 10.10 (rev 1574618)

Java DB testing and reporting infrastructure. Failure nightly 10.10 (rev 1574618) There were 2 failures. Test report: http://download.java.net/javadesktop/derby/request_5588435

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

Java DB testing and reporting infrastructure. Failure continuous trunk (rev 1574752) There were 1 failures. Test report: http://download.java.net/javadesktop/derby/request_5588437

[jira] [Commented] (DERBY-6175) testComparisonAcrossPages failure - java.sql.SQLNonTransientConnectionException: No current connection.

[ https://issues.apache.org/jira/browse/DERBY-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922047#comment-13922047 ] Marco commented on DERBY-6175: -- Hi Knut, thanks a lot for your reply! And sorry for my late

[jira] [Commented] (DERBY-6175) testComparisonAcrossPages failure - java.sql.SQLNonTransientConnectionException: No current connection.

[ https://issues.apache.org/jira/browse/DERBY-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922053#comment-13922053 ] Marco commented on DERBY-6175: -- I just took a look at DERBY-4160 which I obviously encounter