Re: [sqlalchemy] dialect issue with pyodbc.Row type

Thanks for the insights On Tue, Jan 9, 2018 at 10:23 PM Mike Bayer wrote: > On Tue, Jan 9, 2018 at 8:45 PM, Russ Wilson wrote: > > So i loaded and tested the mmsql dialect and it gave the same results. It > > returns a list of pyodbc.Row > > > >

Re: [sqlalchemy] dialect issue with pyodbc.Row type

On Tue, Jan 9, 2018 at 8:45 PM, Russ Wilson wrote: > So i loaded and tested the mmsql dialect and it gave the same results. It > returns a list of pyodbc.Row > > from sqlalchemy import Column, Integer, String > from sqlalchemy.ext.declarative import declarative_base > from

Re: [sqlalchemy] dialect issue with pyodbc.Row type

So i loaded and tested the mmsql dialect and it gave the same results. It returns a list of pyodbc.Row from sqlalchemy import Column, Integer, String from sqlalchemy.ext.declarative import declarative_base from sqlalchemy import create_engine from sqlalchemy import Table, Column, Integer,

Re: [sqlalchemy] dialect issue with pyodbc.Row type

There's the README at https://github.com/zzzeek/sqlalchemy/blob/master/README.dialects.rst which also includes some links to an example dialect. On Jan 9, 2018 12:35 PM, "Russ Wilson" wrote: Is there a good doc that covered at at min needs to be extended to create a dialect?

Re: [sqlalchemy] dialect issue with pyodbc.Row type

Is there a good doc that covered at at min needs to be extended to create a dialect? On Mon, Jan 8, 2018 at 3:15 PM Mike Bayer wrote: > On Sun, Jan 7, 2018 at 9:07 PM, Russ Wilson wrote: > > I noticed if you use the cursor.fetchmany it returns the

Re: [sqlalchemy] dialect issue with pyodbc.Row type

On Sun, Jan 7, 2018 at 9:07 PM, Russ Wilson wrote: > I noticed if you use the cursor.fetchmany it returns the pyodbc types. Is > this an issue with the dialect? if you use the connection execute you are > correct it returns a resultrow. Thanks for the help. > > cursor =

Re: [sqlalchemy] dialect issue with pyodbc.Row type

I noticed if you use the cursor.fetchmany it returns the pyodbc types. Is this an issue with the dialect? if you use the connection execute you are correct it returns a resultrow. Thanks for the help. cursor = connection.cursor() cursor.execute("SELECT * FROM mytable") results_one =

Re: [sqlalchemy] dialect issue with pyodbc.Row type

On Jan 7, 2018 11:29 AM, "Russ Wilson" wrote: When I attempt to create a panda dataframe from the results it throws this error "Shape of passed values is (1, 100), indices imply (9, 100)" because it is seeing the results as 1 column vs a list of columns. Ill take a look at

Re: [sqlalchemy] dialect issue with pyodbc.Row type

When I attempt to create a panda dataframe from the results it throws this error "Shape of passed values is (1, 100), indices imply (9, 100)" because it is seeing the results as 1 column vs a list of columns. Ill take a look at the SQL Server one. Thanks pd.DataFrame(data=data,

Re: [sqlalchemy] dialect issue with pyodbc.Row type

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

[sqlalchemy] dialect issue with pyodbc.Row type

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/