You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2004/11/28 06:07:21 UTC

[jira] Resolved: (DERBY-33) Connection.setTypeMap throws unimplemented exception with empty map

     [ http://nagoya.apache.org/jira/browse/DERBY-33?page=history ]
     
Daniel John Debrunner resolved DERBY-33:
----------------------------------------

    Resolution: Fixed

Sending        java\engine\org\apache\derby\iapi\reference\SQLState.java
Sending        java\engine\org\apache\derby\impl\jdbc\EmbedCallableStatement20.java
Sending        java\engine\org\apache\derby\impl\jdbc\EmbedConnection20.java
Sending        java\engine\org\apache\derby\impl\jdbc\EmbedResultSet20.java
Sending        java\engine\org\apache\derby\loc\messages_en.properties
Transmitting file data .....
Committed revision 106787.

Fix for Derby-33 - not implemented exception when passing in empty type map to JBDC calls.

Handling the map conditions the following way

  null Map      --> throw a SQLException
  empty Map     --> no-op
  non-empty Map --> throw notImplemented.

Patch contributed by Shreyas Kaushik (Shreyas.Kaushik@Sun.COM)


> Connection.setTypeMap throws unimplemented exception with empty map
> -------------------------------------------------------------------
>
>          Key: DERBY-33
>          URL: http://nagoya.apache.org/jira/browse/DERBY-33
>      Project: Derby
>         Type: Bug
>   Components: JDBC
>     Versions: 10.0.2.0
>     Reporter: Daniel John Debrunner
>     Priority: Minor

>
> With some other unimplemented methods Derby accepts a default value or value that is in effect a no-op. In this case an empty map should be accepted. May want to apply the same logi to other JDBC methods that take a type map.
> Original bug discovered by Edward Rayl
> http://nagoya.apache.org/eyebrowse/ReadMsg?listName=derby-user@db.apache.org&msgNo=43

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira