Perhaps it is related to the fact(according to mysql documentation) that mysql will silently change the char(32) field (which shows as char(32) in the schema) to a varchar(32) that is actually stored.
If you describe the table from mysql, it shows char(32), perhaps this was read to generate the entities, and somehow the validation is finding about the silent change in column type. According to mysql documentation (13.1.5.1. Silent Column Specification Changes), "this does not affect how you use the columns in any way". Since hibernate is generating the java, and doing the validation, it may be a hibernate bug, nothing to do with seamgen? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098624#4098624 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098624 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
