On Wed, Oct 29, 2008 at 1:29 AM, Adam Nelson <[EMAIL PROTECTED]> wrote:
>
> Proposal:
>
> After running into numerous 'gotcha' type problems with django-contrib
> and django-hotclub on MySQL and looking at some of the MySQL code ,
> I'd like to propose that Django have an official minimum MySQL version
> for the Django core and possibly a higher recommended version for
> contrib, hotclub, and any portable Django apps/snippets/libraries.

I'm not convinced an 'official minimum' is the right way to handle
this. Like it or not, Django does largely work with MySQL 3.23, and
MySQL 3.23 is still deployed in the wild. There are limitations, to be
sure, but if you're aware of (and are willing to work around) the
myriad issues, there is nothing preventing you from using old versions
of MySQL with Django.

The docs already contain a description of the potential problems and
limitations, much like the list you compiled:

http://docs.djangoproject.com/en/dev/ref/databases/

If you have any suggestions on how to improve these notes, feel free
to open a ticket with your suggestions.

> This effectively means that any server built in 2008
> already has MySQL 5.0 running on it.

No - it means that any server built in 2008 using Debian Etch has
MySQL 5.0 running on it. There are many operating systems that are not
Debian Etch, and there are many institutions that won't install the
latest version just because it is the latest (even taking into account
Debian's glacial release schedule). For example, just last week I
worked on a brand new server installation... of RedHat Enterprise
Linux 4, with a shiny new MySQL 4.1 on it. Institutional policy often
overrides release schedules, and the larger the organization, the
larger the inertia when it comes to updating versions.

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 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to