[patch] History always records changes to boolean fields

I always come across theis defect? today. As far as I can see with pdb the self.original_object has 'boolean'-values as 0 and 1, while the new_object has the correct boolean values True and False.

I think that the problem is located in the manager/queryset/loader of the original_object. Didn't found were it is exactly.

solution: don't check str()-values, check real values instead

Alternative approach that also ignores auto_now and auto_now_add fields

I've added another patch that avoids the duplicate code in the first attached patch. Also, it ignores changes to auto_now and auto_now_add fields, which were also polluting the admin history.

Is this something that's likely to make it in before 1.0 or should I go with patching. This is the last piece I need to make my client happy.

I also needed this patch. Same as the last one attached here with the addition of the float case. Without it, I was getting FloatFields? changing every time as well.

-                if not f.primary_key and str(getattr(self.original_object, f.attname)) != str(getattr(new_object, f.attname)):
+                if f.primary_key or getattr(f, 'auto_now', None) \
+                                 or getattr(f, 'auto_now_add', None):
+                    continue
+                newval = getattr(new_object, f.attname)
+                if type(newval) is bool:
+                    cast = bool
+                elif type(newval) is float:
+                       cast = float
+                else:
+                    cast = str
+                if cast(getattr(self.original_object, f.attname)) != cast(newval):

I cannot reproduce. My guess is that this disappeared with newforms-admin, since all of the above code is manipulator related, which no longer applies. Please re-open if it is still an issue, with more details about how to reproduce since I can't do so currently.