db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2453) client and embedded differ for return value for PreparedStatement.getMetaData if there is no ResultSet returned
Date Wed, 14 Mar 2007 20:01:09 GMT

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

Kathey Marsden updated DERBY-2453:
----------------------------------

          Component/s: Newcomer
                       JDBC
    Affects Version/s: 10.3.0.0

> client and embedded differ for return value for PreparedStatement.getMetaData if there
is no ResultSet returned
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2453
>                 URL: https://issues.apache.org/jira/browse/DERBY-2453
>             Project: Derby
>          Issue Type: Task
>          Components: JDBC, Newcomer
>    Affects Versions: 10.3.0.0
>            Reporter: Kathey Marsden
>
> Embedded will return a null value for PreparedStatement.getMetaData() if no ResultSet
is returned.  Client will return a ResultSetMetaData object with 0 columnCount.  Looking at
the javadoc for getMetaData() it says it returns
> "the description of a ResultSet object's columns or null if the driver cannot return
a ResultSetMetaData object"
> So I am not sure which is the preferable behavior, but it should be the same.

-- 
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