UserType to persist ENUM as String-problems with DB mapping

szymic1 · **Joined:** Mon Feb 09, 2004 6:43 am **Posts:** 35

Hi
Based on article "UserType to persist ENUM as String" I've created version that persist ENUM to intiger. I've changed all references from String to integer (or Integer because part of classes use Map).
But I do not why my field are always maped to "varchar(xx) binary" (under MtSQL using schemeexport tool) but I think this field should mapped to integer. To be honest original version also mapped to "varchar(xx) binary" instead "varchar(xx).

But I do not know what is wrong.
All sources are available here: michal.szymanski.free.fr/tmp

Any sugestions ?

Michal

szymic1 · **Joined:** Mon Feb 09, 2004 6:43 am **Posts:** 35

I do not understand why PersistentEnum is deprecated? New suggested enum solution is too complex for typical situation!

Michal Szymanski

christian · **Posted:** Sat May 22, 2004 4:09 pm

PersistentEnum is a keyword in JDK 1.5 and you shouldn't use Hibernate APIs in your persistent classes anyway. It was a bad idea in the first place.

michael · **Posted:** Sat May 22, 2004 6:36 pm

It should be fairly trivial to have all your enums implement a common interface and write a UserType which persists all of them. This only adds an additional type="yyy" declaration to all the enum properties, and we think thats bearable.