Thanks for the link, looks like I need to read some code<g> def instrument_class(self, mapper, class_) appears to be part of the MapperExtension class
-j On Feb 25, 4:13 am, "Gaetan de Menten" <[EMAIL PROTECTED]> wrote: > On Sun, Feb 24, 2008 at 11:13 PM, dundeemt <[EMAIL PROTECTED]> wrote: > > > Has anyone ever tried to create a way to instrument field accesses? I > > am thinking of ways to determine candidates for deferred columns and > > lazy relationships and query times. Currently data optimizations are > > an art, you need to know when and how your data is used, then you > > usually create mock ups of optimizations scenarios and then implement > > them in your code and compare timings. > > > If you could flip a switch and turn on instrumenting you could get > > back hard data during real usage. It wouldn't solve the whole puzzle > > but it would help point out problem areas. > > You should be able to do that with a mapper extension: > Seehttp://www.sqlalchemy.org/docs/04/mappers.html#advdatamapping_mapper_... > > -- > Gaëtan de Mentenhttp://openhex.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SQLElixir" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlelixir?hl=en -~----------~----~----~----~------~----~------~--~---
