Ya, the post_populate hook w/b great -- getting the callback to work was kinda tricky, and I'm worried calling back to internals like that. Calling signatures often change on internals.
On 1/25/07, Michael Bayer <[EMAIL PROTECTED]> wrote: > > yup that would be how you can do that right now. > > i mean, I had this vision of SA being used inside of frameworks which > would provide their own hooks for these kinds of things, i.e. post- > query etc. which is why i dont like to add too many hooks *inside* > unless absolutely necessary. > > but yah if populate_instance() is doing it for you I dont see > anything wrong with that....(did you want a post_populate_instance() > hook or something like that ?) > > On Jan 24, 2007, at 11:07 PM, Rick Morrison wrote: > > > > > What's the best way to perfom a bit of manipulation on a mapper-loaded > > instance just AFTER it's been populated? > > > > Right now I'm using a mapper extension to override populate_instance > > and then calling back to the mapper argument to do the actual > > population, then adding my changes, but is that the best way? > > > > Thx, > > Rick > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
