Regresion - defaultNullValue in addNotNullConstraint is interpreting the value as a String instead of an Int
Description
Environment
Postgres 9.0
Activity
Show:
Manuel Rego Casasnovas April 16, 2012 at 5:55 AM
Thank you very much
Nathan Voxland April 15, 2012 at 3:25 PM
Applied supplied patch
Norman Seidel April 14, 2012 at 10:27 PM
For varchar on MySQL strings will be surrounded by singe quotes (as additional information for Falko Modlers comment). This doesn't work for us because we use hibernate framework and the column is an enum in Java. When hibernate loads from database it complains because 'XY' cannot be mapped to/ is not the same as XY.
Laird Nelson March 31, 2012 at 10:07 PM
In case it matters, this is also true with dates. That is, a defaultNullValue of, say, 2012-03-31 is interpreted as a String, not a date. I mention this because my quick cursory glance at the linked pull request seemed to show that the pull request was checking for explicit types (like BOOLEAN) but did not include DATE among its types.
Nathan Voxland January 24, 2012 at 7:36 AM
Thanks, I'll take a look soon
I have a changeSet like this:
<addNotNullConstraint schemaName="asdfas" tableName="asdfas" columnName="asdfas" columnDataType="INT" defaultNullValue="1" />
It worked fine in version 2.0.0