Re: [sqlalchemy] ValueError from orm/persistance on db.commit()

Thanks for the response and the link to the associated method, there was indeed a numpy datatype (not) being serialized on the linux platform codebase. Numpy has become second nature; I apparently cannot distinguish between it's errors and python errors! On Saturday, June 27, 2015 at

Re: [sqlalchemy] ValueError from orm/persistance on db.commit()

so as these issues tend to be reported in pairs, literally there is a similar issue against geoalchemy2 where the same code is causing a problem. 0.9 does this same comparison but it doesn't attempt to evaluate the __bool__ of the object so I'll fix that:

[sqlalchemy] ValueError from orm/persistance on db.commit()

Hi, I wonder if anyone can help with the below stack-trace. The code in question works perfectly under Windows to MSSQL with the following connection string (params omitted): ENGINE = sa.create_engine('mssql://DBSERVER/DB?trusted_connection=yes') but something becomes an array when the

Re: [sqlalchemy] ValueError from orm/persistance on db.commit()

On 6/26/15 6:42 PM, Tim Pierson wrote: Hi, I wonder if anyone can help with the below stack-trace. The code in question works perfectly under Windows to MSSQL with the following connection string (params omitted): ENGINE =