> OK, sourceforge's SVN is back up and from a brief look I don't think the tip > of the trunk for MySQLdb is intended to be in general use. The comment > associated with rev 530, current for connections.py and the one which > introduced this change is: "Tons of changes from major refactoring/cleanup. > This is all really broken right now. In particular, all results are returned > as strings." > > Sounds like there are major changes going on and picking up a non-released > revision is a bad idea.
Agreed, that was the root of my mistake. However, it strikes me that a change of this nature is not something accidental, so it is probably really coming... eventually. Updating the mysql backend to deal with it robustly is probably a smart move. I have emailed Andy Dustman (the principal developer on MySQLdb) and asked about this change; once I hear back from him we'll know whether a patch needs to be made. TK --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
