When using the following code:

List ReportResult = session.createSQLQuery("select ......").setResultTransformer(Transformers.ALIAS_TO_ENTITY_MAP).list();
Map m = ( Map ) ReportResult.get(0);
Iterator keys = m.keySet().iterator();
while (keys.hasNext()) {
logger.debug( (String)keys.next());
}

the order of the returned keys does not correspond to the order of the fields in the query, as a matter of fact, it does not correspond to any specific order. Shouldn't this leave the order unchanged?

shouldn't this be filed as a bug?

From http://java.sun.com/j2se/1.4.2/docs/api ... l/Map.html

"The order of a map is defined as the order in which the iterators on the map's collection views return their elements. Some map implementations, like the TreeMap class, make specific guarantees as to their order; others, like the HashMap class, do not."

It seems to me that the Map itself may not guarantee any order. Am I missing something? Is there some hibernate doc/spec that guarantees the order for the implementation of that particular map?

Marius

the main purpose of the map is to be able to access it by an alias key instead of by a integer position into an Object[], so no it is not a bug.

If you want to maintain the sequence then customize the resulttransformer to use something like a SequencedHashMap to get the behavior you want.

I don't think this is a bug. Maps don't have a guaranteed ordering of keys. If you want a repeatable order, you have to use LinkedHashMap.

oops, I didn't see the previous response.