> > Yields an error with MySQL and works just fine for sqlite and PostgreSQL.
> > I guess that's because MySQL Python driver cannot handle unicode queries
> > while others can.
> 
>    Others cannot, too. The query will choke on SQLite.

Well, it works for me on Windows.

Not sure about SQLite version I use though, but connection uri was 
"sqlite:///:memory:"
 
> > The question is whether this behavior will be continued forever or has a
> > chance to be fixed (either in current codebase or in SQLObject 2).
> 
>    I would very much like to fix the feature. Actually I have been spending
> last few days to think about it. Unfortunately it's a hard task in the
> current codebase. I think I need to start a 0.9-branch and do a lot of
> changes in the SQLObject internals to fix this "minor" problem.

I see.

> > Oleg said before that this is a "feature".
> 
>    Never. It is a wart, a very unhappy misfeature.

Oh, sorry then. Glad I was mistaken on the subject.
 
Still looks the chances are slim that this problem will be fixed in the 
foreseeable future. ;(



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
sqlobject-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss

Reply via email to