!NotSupportedError on latest SVN update

[Gerry Steele]

I just upgraded to latest SVN to get some new functionality and
everything broke:

NotSupportedError at /vection/projects/
server is too old to set charset
...
Exception Value:
server is too old to set charset
Exception Location:
/usr/lib/python2.3/site-packages/MySQL_python-1.2.2-py2.3-linux-i686.egg/MySQLdb/connections.py
in set_character_set, line 280

I'm running debian sarge (I don't have time to upgrade right now as I'm
doing some important work):
mysql Ver 12.22 Distrib 4.0.24, for pc-linux-gnu (i386)

[Malcolm Tredinnick]

On Sat, 2007-04-28 at 10:40 +0100, Gerry Steele wrote:
> I just upgraded to latest SVN to get some new functionality and
> everything broke:

Updated from how long ago? Last week? 0.95? 0.91?

> NotSupportedError at /vection/projects/
> server is too old to set charset
> ...
> Exception Value:
> server is too old to set charset
> Exception Location:
> /usr/lib/python2.3/site-packages/MySQL_python-1.2.2-py2.3-linux-i686.egg/MySQLdb/connections.py
> in set_character_set, line 280
>
> I'm running debian sarge (I don't have time to upgrade right now as I'm
> doing some important work):
> mysql Ver 12.22 Distrib 4.0.24, for pc-linux-gnu (i386)

As a quick fix until you have time to work it out in more depth, switch
to the mysql_old backend.

I thought we were still MySQL-4.0 compatible, but maybe that isn't
correct any longer. This warrants a bit more poking around.

Regards,
Malcolm

[Gerry Steele]

Malcolm Tredinnick wrote:
> Updated from how long ago? Last week? 0.95? 0.91?
>

Well
I've always been using SVN and i ran SVN update this morning.

4759 is the most recent update i can run.

[Malcolm Tredinnick]

Okay, so that's a little bit before 0.96 was tagged. Thanks for the
precise changeset number. In [4760], a change was made that actually
fixed some problems, but introduced what is almost certainly the issue
you're seeing.

I've just open ticket #4179 so that we don't forget to look at this.

Regards,
Malcolm