I noticed in other enum related posts ( specifically
http://forum.hibernate.org/viewtopic.php?t=946264 ) that with annotations you can have hibernate map the enum based on the underlying DB column type.
Although it is not a desirable solution, I edited the DDL for the InGenre table to:
Code:
create table InGenre (isbn varchar(255) not null, genre varchar(255) not null )
thinking that maybe the problem was only with the schema export and that hibernate would pick up on the mapping. Unfortunately, this is what I got:
Code:
(util.JDBCExceptionReporter 72 ) null, message from server: "Unknown column 'elt' in 'field list'"
So, why does the inverse column mapping get ignored completely? I can't even specify the name, much less the type or other constraints, and we can't go around with
elt as the name of all our 'weird' columns.
Furthermore, I don't want to have to maintain the DDL by hand, this is a small reference application we are working on right now, but when we start to have multiple columns like this, going back and fixing the generated DDL every time we change it is going to become a nightmare.