Correct handling of boolean field types in utils.py

[wcalvert]

I believe there's a small bug in the function get_model_from_dictionary. When a value of "False" is assigned to a field of type BooleanField, it was getting converted to True. This is probably because in Python, bool("False") converts to True.

[coleifer]

This assumes you are serializing your boolean fields using 'True' and 'False' I guess?

[wcalvert]

That's correct. I shouldn't have used the word "bug" because it's really only related to cases of 'True' or 'False' and not True or False.

[loleg]

I am unable to correctly filter boolean fields on both 0.6.5 and master through the REST API, applying this patch did not seem to fix the issue, but I have a feeling it's a related problem. Anything in the __ne filter gives no results, and the __eq filter does not have any effect.

[antback]

I'm suffering this bug, too. In my model class, the field is defined as BooleanField() and in the database MySQL is defined as tinyint(1). Any filter by this field using the REST api is ignored as allways put 1 in the query.