This is a bit of a bazaar one as far as i'm concerned but perhaps someone may shed some light on it.

Setup:

Tomcat 4.0.x, Hibernate 1.2.5 using dbcp for pooling, Postgresql 7.3.4, j2se 1.4.x

Problem:

When using a sorted set with a custom comparitor if there is only one element in the set hibernate refuses to lazy initialise the set even after calling Hibernate.initalize(set); if there is more than one element everything works fine, only if the is one does it not get intiialized. The element gets written to the database fine. Its only on retrieval that it fails.

if i change it from being a SortedSet to just being a plain set it works fine.

This is not a comparator issue either as far as i can see as i use exactly the same comparator to sort it in my own code (as apposed to the generated classes) and it works fine.

I had a look in JIRA and didn't see anything and didn't find anything in searchs of the old forum or the current one.

any ideas?

ta

(this is just for interests sake as i'm currently working around it)

peedee

what happens if you use sort="natural"?