I want to map a database field VARCHAR(1) with values 'Y', 'N' (and in some cases null) to a boolean (and java.lang.Boolean). When hibernates reads these fields it works fine: 'Y' is tranformed to true and 'N' to false. But when inserting a new record: hibernates uses 1 and 0 in stead of 'Y' and 'N'.

Is there a way to set this up the way i want?

Maybe more details would help...
have you set type to "yes_no" ?
http://www.hibernate.org/hib_docs/refer ... pping-s2-2

Thank you for your reaction. I am testing it now but a quick reaction i can give already. yes_no will not work for java.lang.Boolean.

For example this mapping:


The code generator will generate a boolean member, and not java.lang.Boolean. So i cannot use yes_no there.

I am trying yes_no for boolean right now (so where not-null="true"...) - i will keep you informed if this works, but i am still looking for a mapping solution for java.lang.Boolean!

You asked for some more details. What i want is the database field garden_ind to have the values: 'Y', 'N' and null. I want Hibernate to translate it to their appropriate Boolean value. Retrieving is not a problem, but when I insert a new record, garden_ind will be set to 1, 0, or null and thereby introduce a problem with the legacy software.

yes_no works for boolean. Thank you for the tip!

For others who might try to use it: i use MySQL. MySQL has a nice feature that when you insert 'No' into a VARCHAR(1) it will be stored as 'N'! So - i am not sure if this solution will work for other databases (i guess that most databases will produce an error when you try to insert 'No' in a VARCHAR(1) field).

Anyway - i still need a solution for java.lang.Boolean. Is there a yes_no_null kind of solution?

I have been looking/googling again - but i don't think the java.lang.Boolean works properly in Hibernate. I mean this setting:

only works when retrieving by Hibernate.

I have solved the problem by writing specific setters and getters for java.lang.Boolean. These setters/getters replace the hybernate setters and getters - which are implemented as String now.

For example:


In this example getGarageInd() is generated by Hibernate - but not used in the application.

People must be shot for such "nice features".

Or you can use the hibernate properties for global substitutions:

hibernate.query.substitutions=true 1, false 0, yes 'Y', no 'N'

I agree, I put an ! after my nice feature sentence, trying to put it as a cynical remark...

hibernate.query.substitutions=true 1, false 0, yes 'Y', no 'N' as i posted before - will NOT work.