I think, unfortunately, two branches is the way to go (<=4.1 and 5.0<=)
- there are hosts out there who still provide 3.28, Debian sarge is
4.0.2. So - I guess the question is - what version of MySQL does
Django's backend work with at the moment.
I'm running the patch right now, and haven't seen
On 8/31/06, Geert Vanderkelen <[EMAIL PROTECTED]> wrote:
>
>
> There is already some migration going on from 4.x to 5.0, so I think
> we should go for 5.0 as 'default' backend. But that is just my opinion.
Just remember that all those shared hosting companies are very slow to
migrate at all. I'd
Hi Andy,
On 31 Aug 2006, at 19:40, Andy Dustman wrote:
>
> I've come up with a patch to the MySQL backend. If you use MySQL,
> please check it out.
>
> http://code.djangoproject.com/ticket/2635
>
> One of the issues to resolve is: What is the minimum version of MySQL
> which Django should suppor
I've come up with a patch to the MySQL backend. If you use MySQL,
please check it out.
http://code.djangoproject.com/ticket/2635
One of the issues to resolve is: What is the minimum version of MySQL
which Django should support? I am doing all my development with 5.0,
and the early deployment I h
4 matches
Mail list logo
