Looking at that error, it could only be caused by the DB not sending
strings that are encoded as UTF-8.
Obviously, something's changed in the mysql api. Here's how we tell
MySQL we want things back in UTF-8 (from wikidb.py):
if config.db_type == 'mysql':
d['init_command'] = 'SET NAMES utf8'
d['charset'] = 'utf8'
Maybe the new MySQLdb isn't sending those commands?
I would try adding the following:
if config.db_type == 'mysql':
d['init_command'] = 'SET NAMES utf8'
d['charset'] = 'utf8'
d['use_unicode'] = True
I haven't tried this, so I'm not sure if it will do the trick.
--Philip
On 5/16/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > I was able to build the database on a box running MySQL 5.0.22 (with
> > dbapi python2.4-mysqldb 1.2.1c3-4ubuntu4) with Sapling (at r660).
>
> Thanks for this note. It reminded me that I downloaded the latest version
> of mysql-python (1.2.2). Apparently 1.2.2 does not work with Sycamore
> and/or sapling's buildDB.py script. I fixed my utf-8 problems by
> downgrading mysql-python to version 1.2.1_p2.
>
> I'll update the Dreamhost install page soon.
>
> Scott
>
> _______________________________________________
> Sycamore-Dev mailing list
> [EMAIL PROTECTED]
> http://www.projectsycamore.org/
> https://tools.cernio.com/mailman/listinfo/sycamore-dev
>
_______________________________________________
Sycamore-Dev mailing list
[EMAIL PROTECTED]
http://www.projectsycamore.org/
https://tools.cernio.com/mailman/listinfo/sycamore-dev
