On Jun 20, 2013, at 12:54 PM, Kevin S <kevinrst...@gmail.com> wrote:
> Ah ok, I did not know you could use FreeTDS with pyodbc. It was a bit more > complicated to set up, but I finally got pyodbc installed and working. I > reran my thread tests, and they seem to be working. They don't have the > locking issue anymore. > > However, I have one small (hopefully small) issue when trying to use the > sybase-pyodbc dialect with flask-sqlalchemy. Flask is by default passing a > 'convert_unicode=True' argument to the create_engine() calls when building > its connection pool. It gives the following error on initialization: > > TypeError: Invalid argument(s) 'convert_unicode' sent to create_engine(), > using configuration SybaseDialect_pyodbc/QueuePool/Engine. Please check that > the keyword arguments are appropriate for this combination of components. This is a bug that was reported in the Sybase dialect recently and is fixed in 0.8.2. The convert_unicode flag should be accepted by all dialects. If you go get the 0.8 or master branch from "Development Versions" at http://www.sqlalchemy.org/download.html it should be working. -- 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/groups/opt_out.
