On Wed, May 6, 2009 at 2:05 PM, Maxim Savtchenko <[email protected]> wrote: > Great idea. It should be usefull even in this form. Just one > feature-request - activity logging. If other factor threads are > calling sql-command or sql-query - showing requests and responses in > formatted manner. >
That doesn't sound so easy to do in a db independent way. Sqlite seems to provide an sqlite_trace() callback, but I can't see it in our binding. Postgresql has a PQtrace() but it seems to work just for the current connection and googling around a bit it seems to cause more problems than it solves. Another way would be to create triggers on every table on startup (and to remove them on shutdown), but it is error prone and not quite elegant. Any advice on how I can do it? Anyway, I have a couple of things to do before pushing to github: - parsing custom commands (show/describe table/etc...) with peg for more robust parsing - testing with postgresql - cleaning up the code - writing some documentation :) Bye, Diego ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
