On Monday 20 August 2007 20:58:45 [EMAIL PROTECTED] wrote: > On Monday 20 August 2007 18:09:41 jason kirtland wrote: > > svilen wrote: > > > And anyway i need to first create the object and just then > > > append it (the decorators will first fire event on the object > > > and just then append(), that is call me), so may have to look > > > further/deeper. Maybe i can make my append create objects first > > > and then call the actual appender - so yes, this is the way. > > > > Either way. The @internally_instrumented is there exactly for > > that flexibility on ORM interface methods like 'append' and as an > > override for ABC decoration on python interface methods. (The > > regular recipes also override ABC decoration.) Or you can do > > you work elsewhere and forward to an instrumented method for > > event service. > > an example on this? i can't figure it out, whatever i do, that > ABC-auto-decorators loop kicks in and byebye my nice append - even > if the appender is not append() at all. Why should append() be > instrumented regardless of it being or not the used appender? > so @internally_instrumented prevents any automatic wrapping, ok i got it. (The docstrings in collections.py should make their way to the normal docs...) it is not at all obvious why, if there is a choosen appender, the default one (append() or whatever) has to be instrumented too...
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
