[
https://issues.apache.org/jira/browse/DERBY-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393138#comment-15393138
]
Bryan Pendleton commented on DERBY-3600:
----------------------------------------
After studying the related JIRAs, and looking through the derby-dev archives
for January/February 2008, my feeling is that we should close this issue as
"wont fix".
This issue is 8 1/2 years old, and my instinct is that changing the exception
signatures at this point brings more risk than reward.
I think the most relevant comment is this one, from DERBY-3455:
https://issues.apache.org/jira/browse/DERBY-3455?focusedCommentId=12572846&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12572846
{quote}
I hope there will be a follow-up patch that unwraps the SQLExcpetions into
StandardException for these methods.
{quote}
The use of the term "unwraps" makes me think that the primary concern was that
if one of
these exceptions was raised, it would be wrapped, unnecessarily, in multiple
intermediate
"wrapper" exceptions, which would confuse the diagnose and potentially conceal
the
root cause.
But that concern doesn't seem to warrant modifying this code at this late date.
> Change replication methods in org.apache.derby.iapi.db.Database to throw
> StandardException instead of SQLException
> ------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3600
> URL: https://issues.apache.org/jira/browse/DERBY-3600
> Project: Derby
> Issue Type: Improvement
> Components: Replication
> Affects Versions: 10.6.1.0
> Reporter: V.Narayanan
> Assignee: Danoja Dias
> Priority: Minor
> Attachments: derby-3600.diff
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
