On Jul 16, 2007, at 6:23 PM, Cory Smith wrote:
> > Fair enough. > > I don't remember that in docs. Did I miss a section, or is this too > obscure for the general usage? its only obscure because i think non_primary mappers are not *too* common, but their behavior should be more well defined in the docs (that they dont want to deal with attributes is a big one) > > (Like the time I decided to override the object.__hash__ to work off > the primary key? Made object saving a real treat. couldn't figure out > why I always had orphaned objects in the session.) ahhm ive never tried that....we rely on a lot of set() stuff so yeah, thats another good one to document (or maybe we can find a way to work around it....) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
