On 2/28/07, Geert Vanderkelen <[EMAIL PROTECTED]> wrote: > > Django is, as I have > been told, database independent. And Django is working fine with > MySQL, lets keep it that way.
Well, no, MySQL isn't working fine. Like I said, [4610] didn't break MySQL - it just revealed a problem that has always been there but wasn't being tested. [4610] introduced a test for the problem, and fixed the problem for Postgres. SQLite never had the problem. MySQL still has the problem. Reverting [4610] won't fix MySQL - it only serves to break Postgres, and hide the problem from both. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
