🚀 go-pugleaf

 "Owen Green" <owen@norobots.unique.com> wrote:


> > Because I must do the sort on disk  - there could potentially be
> > gazillions of these records.


> Ah, well I'm just having to go home, but it may interest you to know that if
> you change


>     myDataString.compareTo(myIndexCompareString) < 0
> to
>     myDataString.compareTo(myIndexCompareString) > 0


I made your change and reran. 


> it comes out in perfect reverse order...


It does and it doesn't.


What I mean by that is that if you use the data I provided, then yes,
it does come out in order, but this is only because the first record
to be inserted also happens to be the lowest in lexicographical order.


However, if you use a slightly larger dataset with records which have
codes "lower" than "Ams3vh45", it doesn't work properly.

 
> Sorry not to be of more help, if you haven't cracked it tomorrow I'll have a
> closer play with it...


Thanks for taking an interest. I would be grateful if you could figure
it out, it's been killing me for a while now.


Paul...

 
> Owen