-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Steps 1.) and 2.) are imo ok. the sql contains an order by and ArrayList also maintains the order.
The problem is in step 3.) how could we warn the user that his list may cause sorting problems ?
Yup exactly what I was originally thinking, I do think however that we can just change from a HashSet to a SortedSet, then the ArrayList and *Set Impl will work. HashSet is fine for speed I guess if there is no ordering. So maybe we check to see if we have orderedby and get a SortedSet, if not HashSet. Then document behavior? If not possible, then definitely throw an exception to get the user's attention.
R -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin)
iD8DBQFCB9+tJhqny0eCHK8RAhi5AJ4jyv7T1FqX1op3GJDUcB+IVCD9vgCdFLBf oWyJ2aSiuWC9FVN9aBi1qH8= =wf8c -----END PGP SIGNATURE-----
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
