Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-1288

Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 10.2.1.6
    • Fix Version/s: None
    • Component/s: JDBC
    • Labels:
      None

      Description

      The following statement raises an error in Derby:

      statement.executeQuery( "

      {call foo()}" );

      although this statement works:

      statement.executeUpdate( "{call foo()}

      " );

      According to section 6.4 of the latest draft of the JDBC4 Compliance chapter, both statements are supposed to work in order to claim Java EE JDBC Compliance.

      We need to bring Derby into compliance by supporting executeQuery() on escaped procedure invocations.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                knutanders Knut Anders Hatlen
                Reporter:
                rhillegas Richard N. Hillegas
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: