#2635: [patch] Updates for MySQL backend
--------------------------------------------------+-------------------------
Reporter: Andy Dustman <[EMAIL PROTECTED]> | Owner:
mtredinnick
Status: new | Component:
Database wrapper
Version: SVN | Resolution:
Keywords: | Stage:
Ready for checkin
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------------------------+-------------------------
Changes (by mtredinnick):
* stage: Design decision needed => Ready for checkin
Comment:
Great work, sir. This last patch (and the mysql.txt file) looks like
something we should use. I've read the code once and it looks right from a
"fits in with Django" perspective. I'm deferring to your experience on the
MySQL front. I want to test it out on an older machine that I'll have
access to tomorrow just to see that we haven't hosed bakcwards
compatibility. Given the features this adds and the long break that will
exist between 0.96 and 1.0, if it doesn't break backwards compat in any
obvious way, I think it should go in before 0.96, since it will help with
a lot of peoples' issues.
In the short-term we should fix the testing framework to look inside
DATABASE_OPTIONS and force it to point to django_test_db, but that's
probably not a showstopper for these changes, since it's possible to work
around it in any case.
Thanks a lot for persisting with this and coming up with a non-intrusive
solution.
--
Ticket URL: <http://code.djangoproject.com/ticket/2635#comment:11>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
