Sounds good - thanks for sending that over. I looked high and low for that
document and couldn't find it.
I'll make suggestions in a documentation ticket.
Regards,
Adam
On Tue, Oct 28, 2008 at 7:34 PM, Russell Keith-Magee <[EMAIL PROTECTED]
> wrote:
>
> On Wed, Oct 29, 2008 at 1:29 AM, Adam N
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 ve
My web host is still using 3.32 on the majority of their servers. They
just started upgrading to 5 though and plan on getting all their
servers migrated by the end of the year. Though I dont use MySQL for
django so I dont care what version they are using. I use PostgreSQL,
which my host is running
After further review, I did find some webhosts that are still using
the MySQL 4 series which would be restrictive for some Django 1.0
users.
MySQL 4.1 might be a better minimum.
http://mediatemple.net/webhosting/gs/faq.php
-Adam
On Oct 28, 12:29 pm, Adam Nelson <[EMAIL PROTECTED]> wrote:
> Pro
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, ho
