c2c-oerpscenario team mailing list archive
-
c2c-oerpscenario team
-
Mailing list archive
-
Message #28462
[Bug 808672] Re: improving ir_sequence to rely on its own security rule instead of the company rule
Note that this should only be fixed in trunk after ensuring that the
original merge in 6.0 (mentioned in the description) has already been
forward-ported to trunk
** Summary changed:
- ir_sequence regression
+ improving ir_sequence to rely on its own security rule instead of the company rule
--
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/808672
Title:
improving ir_sequence to rely on its own security rule instead of the
company rule
Status in OpenERP Server:
Confirmed
Bug description:
A few words of explanation: the merge for OPW case 10420 changed the
code of ir.sequence to make it select all sequences that belong to
companies that are visible to the user. This could be improved by
having a default security rule on ir.sequence and use it to select the
visible sequences (by default, all sequences of the currently visible
companies: the current one and its children), instead of using the
companies rules implicitly.
However the code change must be done very carefully, as we must not disrupt the logic of the SELECT FOR UPDATE NOWAIT, used to properly guard concurrent transactions.
See also the comments on the merge, as linked below.
-- original description --
Hello! Please give a look at my comment here https://code.launchpad.net/~openerp-dev/openobject-server/6.0-opw-10420-ira/+merge/66546. I'm opening a bug as well because that branch has been merged already. thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/808672/+subscriptions
References