Created by IT Consulting Srl on 2013-03-06 and last modified on 2013-03-06
Get this branch:
bzr branch lp:~bnfo/aeroolib/aeroolib
Only IT Consulting Srl can upload to this branch. If you are IT Consulting Srl please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

IT Consulting Srl
Aeroo Reporting library

Recent revisions

4871. By Chris Biersbach (OpenERP) on 2013-03-05

[MERGE] OPW 585261: translations: corrects extraction of translation for placeholders

4870. By Launchpad Translations on behalf of openerp on 2013-03-05

Launchpad automatic translations update.

4869. By Quentin (OpenERP) <email address hidden> on 2013-03-04

[MERGE] base, res.users: added onchange_state() on res.users. Was crashing because the _inherits is not a real python inheritance

4868. By Xavier (Open ERP) on 2013-03-04

[FIX] strip server action code before passing it to eval

Python 2.7's compile handles trailing whitespaces correctly, Python
2.6 does not and blows up.

4867. By Launchpad Translations on behalf of openerp on 2013-03-04

Launchpad automatic translations update.

4866. By Olivier Dony (Odoo) on 2013-03-01

[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)

4865. By Olivier Dony (Odoo) on 2013-03-01

[MERGE] registry: another pass of cleanup for registry signaling

Some important points to consider:
 - signaling should be done after any schema alteration (including module [un]installation),
   service registration (e.g. reports)
 - the changes need to be committed to the database *before* signaling, otherwise an
   obvious race condition occurs during reload by other workers
 - any call to restart_pool() must be considered a possible candidate for
   signaling, and the 2 above conditions must be checked

The number of explicit calls was reduced by forcing the signaling at the end of
Registry.new() in case `update_module` was passed as True. In that situation
we always want to signal the changes - so all the redundant signaling calls
can be centralized. We can also assume that the relevant changes have already
been committed at that point, otherwise the registry update would not
have worked in the first place.
This means that there is no need for explicit signaling anymore everytime
`restart_pool` is called with `update_module=True`.

Some missing cr.commit() and explicit signaling calls were added or
moved to the right place. As a reminder: signaling must be done
*after* committing the changes, and usually *after* reloading the
registry on the current worker.

4864. By Christophe Simonis (OpenERP) on 2013-03-01

[FIX] base: allow admin to freeze the value of "web.base.url" config parameter.

This config parameter is automatically updated when the admin log-in.
As this value is mean to be used in emails and links given to users, we sometime don't want
it to be updated inconditionnaly. In some cases, the admin may use alternative, private or
even local uri to connect to the server, which may not be suitable for users

4863. By Launchpad Translations on behalf of openerp on 2013-03-01

Launchpad automatic translations update.

4862. By Olivier Dony (Odoo) on 2013-02-28

[FIX] ir.model: properly signal registry change for multi-process mode after altering model/db schema

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
This branch contains Public information 
Everyone can see this information.