db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Myrna van Lunteren <m.v.lunte...@gmail.com>
Subject Re: [PATCH] (DERBY-276) ResultSet.relative(int row) cannot be called when the cursor is not positioned on a row.
Date Fri, 10 Jun 2005 14:08:14 GMT
On 6/10/05, Bernt M. Johnsen <Bernt.Johnsen@sun.com> wrote: 
> 
> >>>>>>>>>>>> Myrna van Lunteren wrote (2005-06-09
14:17:51):
> > On 6/8/05, Bernt M. Johnsen <Bernt.Johnsen@sun.com> wrote:
> > >
> > > >>>>>>>>>>>> Bernt M. Johnsen wrote (2005-05-27
14:31:39):
> > > > Could anybody review this?
> > >
> > > Well?
> > >
> > > > This patch will make relative() allowed when the cursor is before
> > > > first or after last. It will also let absolute(0) be equivalent to
> > > > beforeFirst().
> > > [..snip..]
> >
> > Well, well!
> > I applied the patch without trouble (I feared it would be out of date
> > already :-) ), built without trouble. It all looks reasonable to me.
> > However, your patch doesn't include a modified master for 
> scrollCursors2?
> > Did you run derbyall?
> 
> The patch does include changes to scrollCursors2 and I have run derbyall
> 
> > Could this change create trouble for any existing applications? i.e. 
> What
> > if someone has programmed an app to do relative(1) in a loop, breaking 
> out
> > when the exception is hit?
> 
> That's a problem since JDBC 2.0 and 3.0 is not compatible for this
> example. I think, anyway, that it's better to be 3.0 compliant than
> 2.0 compliant.
> 
> --
> Bernt Marius Johnsen, Database Technology Group,
> Sun Microsystems, Trondheim, Norway
> 

 Well, I must have made a mistake of some sort - I rebuild & rerun & that 
test (scrollCursors2) *is* fine.
Apologies...
 Myrna

Mime
View raw message