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] Resolved: (DERBY-3783) LOBStreamControl shouldn't throw SQLException
Date Mon, 21 Jul 2008 11:13:31 GMT

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

Knut Anders Hatlen resolved DERBY-3783.

    Resolution: Fixed
    Derby Info:   (was: [Patch Available])

Committed d3783-initCause.diff with revision 678388.

> LOBStreamControl shouldn't throw SQLException
> ---------------------------------------------
>                 Key: DERBY-3783
>                 URL: https://issues.apache.org/jira/browse/DERBY-3783
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions:,
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For:,
>         Attachments: d3783-initCause.diff, derby-3783-1a-dont_throw_sqlexception.diff,
> LOBStreamControl throws three types of exceptions: IOException, SQLException and StandardException.
> All the SQLException are generated/thrown from the code in LOBStreamControl.
> At this level of the code, SQLException should not be thrown, as it is more tedious to
handle both SQLException and StandardException at higher levels.
> I propose to replace SQLException with StandardException in LOBStreamControl. The purpose
of this change is consistency, and also results it slightly less code at higher levels.

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

View raw message