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 "Rick Hillegas (JIRA)" <ji...@apache.org> on 2010/05/18 19:34:43 UTC
[jira] Updated: (DERBY-4070) Embedded and client data sources throw
different exception when a connection attribute is badly formatted
[ https://issues.apache.org/jira/browse/DERBY-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-4070:
---------------------------------
Fix Version/s: (was: 10.6.1.0)
> Embedded and client data sources throw different exception when a connection attribute is badly formatted
> ---------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4070
> URL: https://issues.apache.org/jira/browse/DERBY-4070
> Project: Derby
> Issue Type: Sub-task
> Components: JDBC, Network Client
> Affects Versions: 10.4.2.1, 10.6.1.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Attachments: derby-4070-1a-ds_exception_handling.diff, derby-4070-1b-ds_exception_handling.diff, derby-4070-1c-ds_exception_handling.diff, derby-4070-1d-ds_exception_handling.diff
>
>
> If a connection attribute is badly formatted, for instance if the attribute name is specified without a corresponding value, the embedded and the client data sources throw different exceptions:
> o XJ212: Invalid attribute syntax: bad
> o XJ028: The URL 'jdbc:derby://localhost:1527/wombat;bad' is not properly formed.
> Currently the only client data source affected is ClientDataSource, but the connection pool and XA data sources also have to deal with this issue when DERBY-4067 has been fixed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.