diff options
| author | Olivier Dony <odo@openerp.com> | 2013-04-15 19:52:58 +0200 |
|---|---|---|
| committer | Olivier Dony <odo@openerp.com> | 2013-04-15 19:52:58 +0200 |
| commit | 556e4e76c37419c810bfe0da6b13f2a19c4f0a72 (patch) | |
| tree | 896dba5e4324476cfec6e3b65f3e6748abb6b74f /addons/website/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js | |
| parent | 3bd4cef043141500276e743beb8028e1151d4825 (diff) | |
[FIX] l10n_ro: unique constraints on `vat` and `nrc` columns need to be updated for 7.0 model
With the 7.0 model all accounting-related fields are synchronized
from company to contacts (both are res.partner records), so the
unique check is not a trivial unique constraint. It must be updated
to use a *partial unique index* that applies only to "commercial
entities" and not to contacts. The condition for being a commercial
entity is "is_company is true or parent_id is NULL".
If companies have unique vat/nrc numbers, then their contacts
will be consistent because they are automatically synchronized,
so the uniqueness between contacts does not have to be checked.
(The auto-sync is performed by res.partner automatically and covered
by tests in the "base" module)
bzr revid: odo@openerp.com-20130415175258-l15meqin80sbhggu
Diffstat (limited to 'addons/website/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js')
0 files changed, 0 insertions, 0 deletions
