FYI, I've found the corresponding pymssql bug. I hope for the fix being included in their next minor release.
https://github.com/pymssql/pymssql/issues/185 2014. július 27., vasárnap 16:25:23 UTC+2 időpontban Michael Bayer a következőt írta: > > > On Jul 27, 2014, at 8:58 AM, Viktor Nagy <vikto...@gmail.com <javascript:>> > wrote: > > > > > > /Users/viktornagy/.virtualenvs/odoo/lib/python2.7/site-packages/pymssql.so > in pymssql.Cursor.execute (pymssql.c:6347)() > > > > OperationalError: (OperationalError) (105, "Unclosed quotation mark > after the character string 'BiztKod1_1)s'.DB-Lib error message 105, > severity 15:\nGeneral SQL Server error: Check messages from the SQL > Server\nDB-Lib error message 102, severity 15:\nGeneral SQL Server error: > Check messages from the SQL Server\n") 'SELECT [BIZTOSIT].[BiztKod] AS > [BIZTOSIT_BiztKod], [BIZTOSIT].[Fi\xc3\xb3kVezet\xc5\x91] AS > [BIZTOSIT_Fi\xc3\xb3kVezet\xc5\x91] \nFROM [BIZTOSIT] \nWHERE > [BIZTOSIT].[BiztKod] = %(BiztKod_1)s' {'BiztKod_1': 1} > > > > Nota bene, that the Table object was built with reflecting the existing > table. > > > > Do you have any idea how to allow querying with the accented columns > being included? > > > the query looks fine, unless you can point out where it's incorrect, I’m > not seeing this unclosed quotation mark it refers to. So this may perhaps > be a pymssql issue? Does the query above run directly in a pymssql > cursor, and if not, why not ? > > > > > > > -- 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.
