db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre" <mcintyr...@gmail.com>
Subject Re: [jira] Resolved: (DERBY-2358) Exception during multi-row update if a value to be set is a parameter and is set using a streaming inteface, such as setBinaryStream.
Date Tue, 20 Feb 2007 20:17:48 GMT
On 2/20/07, Kristian Waagan <Kristian.Waagan@sun.com> wrote:
> Daniel John Debrunner (JIRA) wrote:
> >      [ https://issues.apache.org/jira/browse/DERBY-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> >
> > Daniel John Debrunner resolved DERBY-2358.
> > ------------------------------------------
> >
> >     Resolution: Duplicate
> >
> > Duplicate of DERBY-2111
> Just a general question:
> When we get duplicates, like this, is it okay to close it at once, or
> should it follow the state of the duplicate issue?
> I'm an advocate of closing Jira issues when they can be closed, that's
> why I ask :)

Duplicates should always be resolved at once, with the resolution of

They should also be closed, JIRA currently shows 388 (!) issues
resolved but not closed. We should bring that number down. You can
view the JIRA issues that you reported that are not yet closed with
the following JIRA filter:


Although I suspect that a lot of the issues that are resolved but not
closed were reported by people who are not reading derby-dev. :-)


View raw message