On 10 Jul 2005, at 15:19, John Peacock wrote:
So there seem to be a couple of ways to approach this:
1) Add either a $transaction->{_connection} or $transaction->{_qp}
element, so that the transaction can crawl back up to it's containing
objects to log using the cached logging plugin.
2) Create a global logging object that everything can use (instead of
binding the logging to the top level object).
3) Create a global size_threshold variable (much like the way that the
spool_dir is a global scalar) and just copy that into every new
$transaction object in reset_transaction.
If it's just a re-defined warning, why not fix the plugin compiler to
not recompile if they've already been loaded? I think I have a patch
for that as part of high_perf, fwiw.
