> One small point to bear in mind - for many of us there IS no SQL. It depends > on the database in use (and your style of using it, I guess).
> It seems to me that the instrumentation (in terms of timing at least) should > be at the boss_db level so that it applies to ALL databases - then the > individual database drivers are free to add some extra info, such as the SQL > used (for a SQL database), or the strategy/models/whatever selected (for the > no-SQL databases). > > I use Mnesia, so I am not sure I can even spell SQL any more, but I too > would like to know where my database time is being spent because it can also > give valuable insights into possible inefficiencies in the app e.g. > re-reading the same record multiple times. I think that for anything, you're going to want the underlying query and how long it took. That requires some code specific to that particular database. I suppose things could be added at a higher level for timing - it depends if you want to time just the underlying DB, or the whole layer. Both are probably useful numbers. -- David N. Welton http://www.welton.it/davidw/ http://www.dedasys.com/ -- You received this message because you are subscribed to the Google Groups "ChicagoBoss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at http://groups.google.com/group/chicagoboss. To view this discussion on the web visit https://groups.google.com/d/msgid/chicagoboss/CA%2Bb9R_uhtoWb2htsy34UMVTc5gR9ZZVE_S5WXSHric3Adc%2Bfjg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
