pyodbc.Row acts like a tuple so there is no special conversion needed.
SQLAlchemy has three pyodbc dialects, for SQL Server (very stable),
MySQL (sorta works), and Sybase (probably doesn't work), but you can
use the first two as examples for the basics. They base off of the
PyODBCConnector in
I was attempting to create a new dialect but hit and issue. pyodbc is
returning a list of pyodbc.Row. Is there a method i should be implementing
to convert the list to a list of tuples.
Thanks
--
SQLAlchemy -
The Python SQL Toolkit and Object Relational Mapper
http://www.sqlalchemy.org/
On Sat, Jan 6, 2018 at 3:31 PM, Florian Apolloner wrote:
>
>
> On Saturday, January 6, 2018 at 8:53:41 PM UTC+1, Mike Bayer wrote:
>>
>> Can you confirm the exact sql and parameters you are seeing? SQLAlchemy
>> never sends NULL for an auto increment id column, it omits it
On Saturday, January 6, 2018 at 8:53:41 PM UTC+1, Mike Bayer wrote:
>
> Can you confirm the exact sql and parameters you are seeing? SQLAlchemy
> never sends NULL for an auto increment id column, it omits it from the
> statement so that the default takes place, which I assume is what you mean
Can you confirm the exact sql and parameters you are seeing? SQLAlchemy
never sends NULL for an auto increment id column, it omits it from the
statement so that the default takes place, which I assume is what you mean
by "leave it out".
On Jan 6, 2018 1:52 PM, "Florian Apolloner"
Hi,
Informix mostly follows the Postgresql behavior when it comes to SERIAL
columns with one notable exception: I have to specify 0 (0 as int, not
NULL) for a SERIAL column on insert or leave it out.
Code like:
```
Table('date_table', metadata,
Column('id', Integer,
use `sqlalchemy.orm.aliased` to create an alias of A for your join
condition...
A_alt = sqlalchemy.orm.aliased(A, name='a_alt')
then use that to join and specify your join conditions
the `contains_eager` needs to specify the alias though.