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

Client and embedded behave differently when the table name is null in DatabaseMetaData methods

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 10.2.1.6, 10.3.1.4
    • Fix Version/s: 10.3.1.4
    • Component/s: JDBC, Network Client
    • Labels:
      None
    • Issue & fix info:
      Release Note Needed

      Description

      When giving null as table name to getBestRowIdentifier, getColumnPrivileges, getIndexInfo, getVersionColumns or getPrimaryKeys, the client driver fails with "SQLException: Table name can not be null". Embedded uses null as a wildcard and does not fail. Embedded and client should have the same behaviour.

        Attachments

        1. DERBY-1484.diff
          8 kB
          Jorgen Loland
        2. DERBY-1484.stat
          0.7 kB
          Jorgen Loland
        3. DERBY-1484-2.diff
          8 kB
          Jorgen Loland
        4. DERBY-1484-2.stat
          0.2 kB
          Jorgen Loland
        5. DERBY-1484-3.diff
          9 kB
          Jorgen Loland
        6. DERBY-1484-3.stat
          0.2 kB
          Jorgen Loland
        7. DERBY-1484-4_ExcFact.diff
          8 kB
          Jorgen Loland
        8. DERBY-1484-4_ExcFact.stat
          0.3 kB
          Jorgen Loland
        9. releaseNote.html
          3 kB
          Myrna van Lunteren
        10. releaseNote.html
          3 kB
          Jorgen Loland
        11. releaseNote.html
          3 kB
          Jorgen Loland

          Issue Links

            Activity

              People

              • Assignee:
                jorgenlo Jorgen Loland
                Reporter:
                knutanders Knut Anders Hatlen
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: