Many thanks for the prompt reply.
if you are getting that error on INSERT it sounds like there are driver
> issues involved (e.g. pymssql, pyodbc). For an INSERT you should not
> get that error; using the VARBINARY SQLAlchemy type, SQLAlchemy calls
> upon a construct provided by your DBAPI
Hi Mike
I don’t need support very often, but when I do I know I can count on your clear
and concise responses to save the day.
Everything was SO close - all I needed to do was take my dynamically created
classes (SalesDocumentLine for example) and force them into the general
globals() and
On 10/03/2016 07:41 PM, Andrew Kowalik wrote:
SQLAlchemy == 1.0.3
mysql-python == 1.2.5
I have been playing around with baked queries and have a couple
observations, one which is problem my lack of SQLA knowledge and the
other a possible feature.
1) .in_ and bindparam
I have a query that I
On Monday, October 3, 2016 at 7:41:09 PM UTC-4, Andrew Kowalik wrote:
>
> I have a query that I am baking that uses in_ with a python list. For
> example
> baked_query += lambda q: q.filter(Model.attr1.in_([bindparam('attr1')])
>
>
Try using a tuple instead of a list. Some Python drivers
