db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (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 Mon, 17 Aug 2009 10:58:14 GMT

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

Knut Anders Hatlen updated DERBY-2453:
--------------------------------------

    Bug behavior facts: [Embedded/Client difference]

> 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
>    Affects Versions: 10.3.1.4
>            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