On Thu, Sep 28, 2006 at 12:27:44PM -0400, Nathan Edwards wrote:
> My solution (this is where my ignorance comes in) is to change the
> default sqlobjct_encoding to 'latin-1'
There is no such thing as default encoding... or at least there should
not be. Those 'ascii' in col.py are really quick-n-dirty hacks made by
MySQLdb-ignorant (me, really). I am going to replace them by
connection.encoding, so you can set the "default" encoding in the DB URI.
Unfortunately, I am too busy, and there are no other active developers.
I'd like to see more people working on SQLObject. A person to maintain
0.7-branch, a few persons to work on the trunk and documentation... I'd
like to concentrate on the paramstyle-branch, and then to work on SQLObject
deep internals. Probably it should be unicode-only instead of
unicode-aware. But that's a distant future...
Oleg.
--
Oleg Broytmann http://phd.pp.ru/ [EMAIL PROTECTED]
Programmers don't die, they just GOSUB without RETURN.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
