Re: [eclipselink-users] OrderBy Annotation

[Tom Ware <tom.ware@xxxxxxxxxx>]

Hi Michael,

  Based on your description, it seems like there is a bug.  When I run our 
tests, however, I do not see this issue.

  Please file a bug and attach some recreation code.

-Fom

Michael Simons wrote:
> Hello,
>
> we've got a collection:
>
> @Entity class Vehicle {
>   @OneToMany(cascade={CascadeType.MERGE, CascadeType.REFRESH, CascadeType.REMOVE},
> fetch=FetchType.LAZY, mappedBy="leadTruck")
>   @OrderBy("seqno ASC")
>   @JoinFetch(value=JoinFetchType.OUTER) // Never remove this, or you will regret it - believe me
> you will.
>   private List<Tour> tours = new ArrayList<Tour>(113);
> }
>
> @Entity class Tour {
>   @Column(name = "seqno")
>   private int seqno = 0;
> }
>
> When the tours of a vehicle are fetched from database the "seqno" of the tours are numbered
> 1,..N regardless of the value "seqno" has in the database.
>
> E.g., the "tour.seqno" values in the database are 43, 44, 45, then we get tours with seqno set
> to 1, 2, 3.
>
> IMHO, according to the specification this is not correct.
> Is this a known bug, or do I misunderstand the specification?
>
> Kind Regards,
> Michael
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-users