Problem described in CORE-1060 was added with the patch in CORE-858.
I'm reverting that patch and sending a new proposal that fix the issue I'm suffering with MySQL described in CORE-858
Regresion - defaultNullValue in addNotNullConstraint is interpreting the value as a String instead of an Int
This reverts commit 8dbe0f0.
addNotNullConstraint not working in MySQL with boolean values
With some of the changes I committed for 3.0 around type management, we may be able to fix this in general without needing to hard-code in the boolean checks. I'll need to do some testing first, though, to try to replicate the problem on 3.0
Once 3.0 is released (or at least an alpha or beta is ready) I can test by myself this issue too. Thanks ;-)