search

bhaumik156 / fsnet

Automatically exported from code.google.com/p/fsnet
0 stars 0 forks source link

Date based consultations are not sorted properly #294

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create a date based consultation
2. Fill in a few dates over several months

What is the expected output? What do you see instead?

One expect the possible dates to be sorted in ascending order.
They do not seem to be sorted at all.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by daniel.l...@gmail.com on 24 May 2011 at 4:05

GoogleCodeExporter commented 9 years ago 
The problem is more difficult that it seems to be : JPA does not save choices 
in the same order as we filled them, when we save all in the same transaction. 
We choose to show choices in alphabetic order, but it's not what you expected 
for dates. 
One solution could be to save each choice in a separated transaction. It does 
not seem very beautiful... What do you think about it ? An other idea ?

Original comment by perrine1...@gmail.com on 24 May 2011 at 4:15

GoogleCodeExporter commented 9 years ago 
I guess that everything is stored as String, right?

I guess that here the elements have to be sorted once you know what they are: 
Date or String.

Original comment by daniel.l...@gmail.com on 24 May 2011 at 4:27

GoogleCodeExporter commented 9 years ago 
Yes it's true. We will try to fix this issue as soon as possible.

Original comment by pierre.d...@gmail.com on 6 Jun 2011 at 4:01

GoogleCodeExporter commented 9 years ago 
fixed in r1991.
http://code.google.com/p/fsnet/source/detail?r=1991

Original comment by pierre.d...@gmail.com on 7 Jun 2011 at 9:38