lp:~therp-nl/openobject-server/7.0-lp1244428-invalid_m2m_assignment_in_test

Branch merges

Propose for merging

No branches dependent on this one.

Ready for review for merging into lp:openobject-server/7.0

OpenERP Core Team: Pending requested 2013-10-24

Diff: 12 lines (+1/-1)

1 file modified

openerp/tests/test_orm.py (+1/-1)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1244428: Invalid many2many encoding in test_orm.py

Low

Confirmed

Link a bug report

Related blueprints

5106. By Stefan Rijnhart (Opener) on 2013-10-24

[FIX] Invalid m2m assignment in test

5105. By Launchpad Translations on behalf of openerp on 2013-10-24

Launchpad automatic translations update.

5104. By Launchpad Translations on behalf of openerp on 2013-10-23

Launchpad automatic translations update.

5103. By Launchpad Translations on behalf of openerp on 2013-10-20

Launchpad automatic translations update.

5102. By Launchpad Translations on behalf of openerp on 2013-10-19

Launchpad automatic translations update.

5101. By Olivier Dony (Odoo) on 2013-10-16

[FIX] document: overridden ORM methods need to respect API idiosyncrasies, otherwise check() calls may fail

5100. By Launchpad Translations on behalf of openerp on 2013-10-15

Launchpad automatic translations update.

5099. By Launchpad Translations on behalf of openerp on 2013-10-13

Launchpad automatic translations update.

5098. By Olivier Dony (Odoo) on 2013-10-11

[FIX] registry: restore `elif` changed to `if` in previous commit, for better readability (no effect)

This should have no effect because when the first `if`
is entered a new registry is instantiated with
the default value for base_cache_signaling_sequence
set to 1, preventing entering the next `if` even
without `elif`.

5097. By Olivier Dony (Odoo) on 2013-10-11

[FIX] registry: avoid discarding registry or cache when the registry is fresh

When the sequence value is 1 it means that either:
 - the registry was just instantiated, so there is no
   reason to reload it immediately, the real checks will
   start at next request
 - the db was just created with new sequences set to 1,
   so there has been no change to reload

In both cases there is no good reason to reload the
registry, and it is actually a performance killer,
especially for cron workers that keep iterating on
the list of databases.