On Thursday, August 15, 2013 12:02:02 AM UTC-4, Michael Bayer wrote:
yes it will always be one element for a scalar reference, a collection for
collections. the ORM internally treats everything like a collection, kind
of another artifact that probably wouldnt have been the case if this API
As previously discussed, i'm using an object's history to log changes to
the database within an application.
http://docs.sqlalchemy.org/en/rel_0_8/orm/session.html?highlight=history#sqlalchemy.orm.attributes.History
Each tuple member is an iterable sequence
I'm trying to figure out when I
yes it will always be one element for a scalar reference, a collection for
collections. the ORM internally treats everything like a collection, kind of
another artifact that probably wouldnt have been the case if this API were
written for end-users originally...
On Aug 14, 2013, at 9:20 PM,
