On Wednesday 28 January 2009 01:34:30 Michael Bayer wrote: > On Jan 27, 2009, at 6:28 PM, a...@svilendobrev.com wrote: > > i have recently stumbled on similar - the rowproxy's __hash__ was > > missing. so i have to tuple() them before usage. > > that doesnt strike me as a similar issue. we should apply that > patch someone had to detect python < 2.6 and place some kind of > callable for __hash__. > > > Then there was Mike's question, what should the RowProxy emulate? > > the tuple of the row, or something else? > > RowProxy is not a buffered object in the general sense so im not > thrilled making it evaluate itself for every tuple() type of > access.
ah, "similar" in the sense of some missing implicit protocol. in this case - __getstate__. nevermind, maybe document it that it's not a good thing to play with ... --~--~---------~--~----~------------~-------~--~----~ 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 sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---