MySQL represents boolean values as 0 and 1, as the BooleanField? documentation warns. This is not an issue when using a NullBooleanSelect? widget, as NullBooleanSelect? translates between model values and arbitrary integers for use in a form. However, not all choice widgets do this and thus they rely on the model values matching the widget values in order to populate initial widget state for rendering. The form field, in turn, must be able to clean the resulting form values. In order to support MySQL, therefore, (Null)BooleanField? must understand '0' and '1'.
Ticket 7753 added support for using HiddenWidget? with the boolean fields, which addresses the general problem of cleaning raw form values. The attached patch adds '0' and '1' to the list of recognized values.
