On 6/27/07, Michael Radziej <[EMAIL PROTECTED]> wrote: > Hi, > > it seems I'm the only one to run the test suite with mysql ;-) > > Ticket #4711 - http://code.djangoproject.com/ticket/4711 > > Currently the tests break because mysql returns 0 or 1 for a BooleanField, > not False or True. Postgresql returns False or True, and for Oracle there's > some special code to make it return False or True (ironically, that's how > the broken test case appeared ...) > > So--what shall be done? Clean it up in a slightly backwards incompatible way > and > make the mysql backend return proper boolean values, or remove the test > case?
Hmm, the test seems to pass for me in mysql. I know that Malcolm edited those test cases specifically to make them pass in mysql when he did the merge -- maybe you've somehow gotten an old version of the file? In any event, looking back at the test case, it should probably just be dropped. The reason we finagled Oracle into returning True/False rather than 1/0 was for consistency because we thought that all the other backends returned True/False, and because we already had similar code in place to convert datetimes. Thanks, Ian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
