db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Løland (JIRA) <j...@apache.org>
Subject [jira] Updated: (DERBY-1484) Client and embedded behave differently when the table name is null in DatabaseMetaData methods
Date Mon, 07 May 2007 11:11:15 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jørgen Løland updated DERBY-1484:
---------------------------------

           Derby Info: [Patch Available, Release Note Needed]  (was: [Release Note Needed,
Patch Available])
    Affects Version/s: 10.3.0.0
        Fix Version/s: 10.3.0.0

> Client and embedded behave differently when the table name is null in DatabaseMetaData
methods
> ----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1484
>                 URL: https://issues.apache.org/jira/browse/DERBY-1484
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client
>    Affects Versions: 10.2.1.6, 10.3.0.0
>            Reporter: Knut Anders Hatlen
>         Assigned To: Jørgen Løland
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>         Attachments: DERBY-1484-2.diff, DERBY-1484-2.stat, DERBY-1484-3.diff, DERBY-1484-3.stat,
DERBY-1484.diff, DERBY-1484.stat, releaseNote.html
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message