Olivier Dony db81edc287 [FIX] *: fix/rationalize db logging to avoid incorrect values during logging ... The setting/clearing of the tracking were not done consistently, causing log messages that appeared to come from one database while coming from another one or none at all. The tracker is now set at the earliest points of request handling where we can: - in web client, when creating WebRequests (dbname, uid) - at RPC dispatching in server (uid) - at cron job acquisition in CronWorker (dbname) - at Registry acquisition in RegistryManager (dbname) The tracker is cleared at the very entrance of the request in the WSGI `application`, ensuring that no logging is produced with an obsolete db name. (It cannot be cleared at the end of the request handling because the werkzeug wrapper outputs more logging afterwards) bzr revid: odo@openerp.com-20130301120744-jfitcmze2jldecod		2013-03-01 13:07:44 +01:00
..
__init__.py	API docs: settings file and titles at modules	2011-06-23 12:03:57 +03:00
expression.py	[FIX] expression: avoid delitem on a tuple	2012-12-17 14:45:59 +01:00
fields.py	[FIX] fields.date[time]: context_today()/context_timestamp() should fallback to user TZ if context TZ is missing	2013-01-12 06:57:17 +13:00
orm.py	[IMP] don't log from import when converting psycopg exceptions to output messages	2013-02-11 15:36:47 +01:00
osv.py	[FIX] *: fix/rationalize db logging to avoid incorrect values during logging	2013-03-01 13:07:44 +01:00
query.py	[REM] unnecessary parens	2012-12-14 13:38:03 +01:00