TRUE is 0?? Do you have a (wrong!) query substitution in your hibernate config files?
TRUE is 01 of course ;)
hmm, query substitution - I have not defined such a configuration and I don't think that this is the problem, because parameter 9 and 10 for example are inserted/updated correctly. The SELECT works for all parameters.
DEBUG [pe.NullableType: 60] binding 'false' to parameter: 9 DEBUG [pe.NullableType: 60] binding 'true' to parameter: 10 DEBUG [pe.NullableType: 60] binding 'true' to parameter: 11
In the hibernate query-log there is no update after this one.
Thank you so far..
No I've inserted
<prop key="hibernate.query.substitutions">true 1, false 0</prop>
into my hibernate-config, but no change with MySQL5.0.
In MySQL4.1 it works!
can we use other substitutions than 1 and 0 for boolean variables
true -1, false 0
and store vlaues -1 for true and 0 for false in database .
i have been trying to do this because in my application, the client is insisting on using -1 for true and o for false in the database.
is it possible, can some one help me.I am using mysql 5
This is a hibernate issue, so better as ik the forums there. (My answer would be that you need to configure it the way the DB wants it, not what the customer wants)