On Wed, 2007-03-21 at 08:03 -0700, Karsu wrote:
> I underestand that mysql_old is compatible support for people who
> can't upgrade MySQLdb immediately. Without this patch I can't use
> django with mysql with older version than MySQLdb-1.2.1p2.
>
> If I try to use mysql_old and run python manage.
I underestand that mysql_old is compatible support for people who
can't upgrade MySQLdb immediately. Without this patch I can't use
django with mysql with older version than MySQLdb-1.2.1p2.
If I try to use mysql_old and run python manage.py syncdb it will
raise ImportError? "MySQLdb-1.2.1p2 or n
On Wed, Mar 21, Karsu wrote:
>
> Please, check this: http://code.djangoproject.com/ticket/3775
I don't think the patch--as it is--is a good idea, but what's your problem?
Michael
--
noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg -
Tel +49-911-9352-0 - Fax +49-911-9352-100
htt
Please, check this: http://code.djangoproject.com/ticket/3775
On 21 maalis, 06:25, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> For the possibly 3.2 people who don't also subscribe to django-users, I
> just posted this
>
> http://groups.google.com/group/django-users/browse_frm/thread/98e6857..
For the possibly 3.2 people who don't also subscribe to django-users, I
just posted this
http://groups.google.com/group/django-users/browse_frm/thread/98e68571ef8ea3a2
describing a way to work around the forced upgrade of MySQLdb if you
cannot do it immediately.
Regards,
Malcolm
--~--~--
