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, Jonathan Vanasco <[email protected]> wrote: > 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 would expect that sequence to have more than > 1 item in it. > > My guess is that for object relationships, it might contain a list of more > than one element -- but for column data it would only be a single element. > is that correct or am I off ? > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sqlalchemy. > For more options, visit https://groups.google.com/groups/opt_out.
signature.asc
Description: Message signed with OpenPGP using GPGMail
