Re: [sqlalchemy] Writing simple dialect for iSeries + pyodbc in order to use "engine.execute" for sql statements.

Thanks for such a quick reply. Great to hear that I am starting out on the right path with building a dialect, I have some work to do so I just wanted to make sure I wasn't missing something before I spend the time. Hopefully I can get things working enough where I can post it somewhere. I ha

Re: [sqlalchemy] Writing simple dialect for iSeries + pyodbc in order to use "engine.execute" for sql statements.

On Jun 7, 2014, at 8:27 PM, Cory Lutton wrote: > I have been looking at using sqlalchemy in an internal company cherrypy > application I am working on. It will need to interface with my companies > iSeries server in order to use ERP data. I have been using pyodbc so far and > everything wor

[sqlalchemy] Writing simple dialect for iSeries + pyodbc in order to use "engine.execute" for sql statements.

I have been looking at using sqlalchemy in an internal company cherrypy application I am working on. It will need to interface with my companies iSeries server in order to use ERP data. I have been using pyodbc so far and everything works great. I am thinking of adding access to another data

Re: [sqlalchemy] Emission of Different DDL for Null and Not Null Columns

On Jun 7, 2014, at 1:21 AM, Michael Weylandt wrote: > I'm working with a database (Sybase ASE) which supports a non-null BIT type. > For Column(Boolean, nullable=False), SQLA's use of BIT is ideal, but I need > to have Column(Boolean, nullable=True) produce a TINYINT + Check constraint. > >