Aaron Long
2014-05-08 17:35:29 UTC
It would be nice to have default column mappings for CompositeUserType's in
hibernate. Is there an existing ticket or any resistance to having Grails
call:
public String[] getPropertyNames();
on a user-type mapping that's composite and use a convention of:
basePropertyName_subPropertyName
similary to embedded types? We use alot of Money and Periods and are
looking at moving to the JSR-310 eventually (using jadira usertypes). This
seems like it would be a nice-to-have convention.
Right now, without a column mapping, you get something like:
property mapping has wrong number of columns: test.Book.published type:
org.jadira.usertype.dateandtime.joda.PersistentDateTimeAndZoneWithOffset
Yeah? Nay?
-Aaron
hibernate. Is there an existing ticket or any resistance to having Grails
call:
public String[] getPropertyNames();
on a user-type mapping that's composite and use a convention of:
basePropertyName_subPropertyName
similary to embedded types? We use alot of Money and Periods and are
looking at moving to the JSR-310 eventually (using jadira usertypes). This
seems like it would be a nice-to-have convention.
Right now, without a column mapping, you get something like:
property mapping has wrong number of columns: test.Book.published type:
org.jadira.usertype.dateandtime.joda.PersistentDateTimeAndZoneWithOffset
Yeah? Nay?
-Aaron