You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-user@db.apache.org by Charles Anthony <ch...@hpdsoftware.com> on 2006/06/20 07:30:52 UTC

RE: Bug : duplicate objects in resultset : Why add orderby column s to resultset?

> -----Original Message-----
> From: Thomas Dudziak [mailto:tomdzk@gmail.com]
> Sent: 19 June 2006 22:26
> Subject: Re: Bug : duplicate objects in resultset : Why add orderby
> columns to resultset?
> 
> 
> On 6/19/06, Janssen, Roger <ro...@ibanx.nl> wrote:
> 
> > Diving deeper into the OJB code I see that the 
> ensureColumns method in
> > fact does two things:
> > (1) add the columns to the returnable set of columns in the 
> resultset
> > (2) adds the columns to a list of columns to be used in force a join
> >
> > (2) is okay for orderby's, but (1) is not. If for orderby's 
> (1) was left
> > out, would that be a problem?
> 
> As far as I remember, there was a problem a couple of months ago that
> for one database all orderby columns had to be selected columns as
> well (though I don't remember offhand which database it was, though).

I don't recall the recent problem, but certainly that was the case for many
years for DB2/400. V5R3 and V5R4 no longer have this problem, though.

Cheers,

Charles.


___________________________________________________________
HPD Software Ltd. - Helping Business Finance Business
Email terms and conditions: www.hpdsoftware.com/disclaimer 



---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org