On 2014-11-29 16:19, Michael Bayer wrote: > SQLAlchemy shouldn’t be attempting to run this decode operation unless the > MySQL driver used here is acting in a flaky way, that is, SQLAlchemy did a > test on first connect to see if a Unicode() type comes back as u’’ or not. > That it’s trying to do the decode means that it didn’t, yet then on this > column it is. > > The MySQL driver in use here would be of top importance in determining why > this might be happening, I guess this is the “gaerdbms” driver?
Yes. > So the best approach for MySQL is to ensure that the driver is predictable > about unicode include, specify use_unicode=0 in the URL (see > http://docs.sqlalchemy.org/en/rel_0_9/dialects/mysql.html#unicode). That's what I did. It helped for a while, then the problem returned. What's going on here? -- http://people.eisenbits.com/~stf/ http://www.eisenbits.com/ OpenPGP: 80FC 1824 2EA4 9223 A986 DB4E 934E FEA0 F492 A63B -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
