SQLAlchemy 0.7.7 is now available. This is the first release of the 0.7 series
subsequent to the promotion of the 0.8 series to trunk. It nearly two dozen bug
fixes and features, including some significant ORM issues that have been
resolved.
Development is now proceeding with the 0.8 series,
SQLAlchemy 0.6.9, a maintenance release of the 0.6 branch, is now available.
The 0.6 series has not seen a release since 0.6.8 was released nearly a year
ago. During that time, the 0.7 series has gone through over six releases,
gaining many new features and bug fixes. A portion of these fixes
List:
I am currently trying to add support for FROM ONLY to the postgresql
dialect. FROM ONLY is used when you wish to query a table which has
other tables that inherit from it, but you ONLY want results from the
parent table you are referencing. More information can be found here:
Hi all.
I'm interested in learning proper application design patterns and best
practices when using a SQLA powered web application (Pyramid based) in a
DB cluster (PostgreSQL 9.1, psycopg2 driver).
The primary requirement for the cluster is realtime backup, so the idea
is to have two or
Hi all.
I'm posting this again because it seems my original post never reached
the list?
I'm interested in learning proper application design patterns and best
practices when using a SQLA powered web application (Pyramid based) in a
DB cluster (PostgreSQL 9.1, psycopg2 driver).
The
On May 5, 2012, at 7:33 PM, Ryan Kelly wrote:
List:
I am currently trying to add support for FROM ONLY to the postgresql
dialect. FROM ONLY is used when you wish to query a table which has
other tables that inherit from it, but you ONLY want results from the
parent table you are
