Olivier Dony e373ac5aeb [MERGE] *: 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 as possible: - in web, 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-20130301182510-1fqo9o8di0jw95b5		2013-03-01 19:25:10 +01:00
..
__init__.py	[FIX] automatically adapt version numbers of modules	2012-08-24 16:23:23 +02:00
db.py	[FIX] module: do not recreate categories when updating modules	2012-11-28 19:37:01 +01:00
graph.py	[REV] reverted install-all commit (vmt@openerp.com-20121128142106-pdkcruhyz0sjltk8)	2012-11-29 15:07:45 +01:00
loading.py	[FIX] registry: another pass of cleanup for registry signaling	2013-03-01 15:32:03 +01:00
migration.py	[IMP] openerp.{modules,osv}: _logger with fully qualified module name.	2012-01-24 13:42:52 +01:00
module.py	[FIX] registry: fix a bug where RegistryManager.new() could return an out-of-date registry.	2013-02-12 09:53:11 +01:00
registry.py	[MERGE] *: fix/rationalize db logging to avoid incorrect values during logging	2013-03-01 19:25:10 +01:00