I just downloaded the latest annotations beta (3.1beta8) and tried using the enum type in a regular, non-annotationed class (with hbm.xml). It was working fine right up until the enum property of a class was used in a query, at which point it blew up on me.

After a little poking around, I was suprised to find this in EnumType.java:



Given that the sqlType is defaulted to Integer, it seems that if you're using a String backing sequence it will work up until it needs to set a value as a bind parameter.

I guess what I'm really wondering is, is there a reason this got commented out? Is this no longer needed if you're running using an AnnotationConfiguration? I've worked around it for now using the 'type' parameter to EnumType. Thanks,[/code]

guessing is fucked up in some databases (including expensive ones) because of lack of decent JDBC metadata support.
Open a JIRA issue with a reproducable test case.

Emmanuel: I'm a little confused. Are you saying that the code is commented out because it causes problems with some JDBC drivers? My problem isn't that the guessing code doesn't work on my DB (it's Oracle...I submitted the patch to make it Oracle friendly), it's that in the latest build the code that should invoke the guessing is commented out.

If you like I can submit a JIRA bug for this. A standalone test case would be a significant amount of work...but a patch, that'd be easy ;)

guessType shouldn't be required anymore as per the spec becasue of the @Enumerated(STRING) annotation.