[sqlalchemy] SQLAlchemy 1.0.7 Released

SQLAlchemy release 1.0.7 is now available. This release contains a series of regression fixes, some additional bugfixes, and a few new Core level features, including a new .cast() method available on column constructs as well as support for many new keywords used in creating sequences. Next

Re: [sqlalchemy] Polymorphic self referential foreign key in sqlalchemy

On 7/20/15 10:49 AM, Douglas Russell wrote: Apologies for cross-posting this, but I realised that this might be a better place to get an answer than this Stackoverflow question that I asked

[sqlalchemy] Polymorphic self referential foreign key in sqlalchemy

Apologies for cross-posting this, but I realised that this might be a better place to get an answer than this Stackoverflow question that I asked a week ago. I am trying to resolve a problem

[sqlalchemy] Re: A glitch: is it SA's, cymysql's or mine only?

Mike Bayer writes: >> and the database accepts it (MySQL is silly, we all know!) but (I guess) >> recognizes that nothing changed and does not return a `rowcount`. > rowcount is still 1 in this case. We set CLIENT_FLAGS against > CLIENT_FLAGS.FOUND_ROWS and that value should never be None if an

Re: [sqlalchemy] A glitch: is it SA's, cymysql's or mine only?

On 7/20/15 4:02 AM, Lele Gaifax wrote: Hi all, I have a rather simple tool that loads data from YAML and put it in the database, using the ORM layer. It designed so that it basically perform what's called an "UPSERT", so I can load the same YAML multiple times with no additional updates. A fe

[sqlalchemy] A glitch: is it SA's, cymysql's or mine only?

Hi all, I have a rather simple tool that loads data from YAML and put it in the database, using the ORM layer. It designed so that it basically perform what's called an "UPSERT", so I can load the same YAML multiple times with no additional updates. A few days ago I got a TypeError exception deep