diff options
| author | Nans Lefebvre <len@odoo.com> | 2019-04-18 07:17:55 +0000 |
|---|---|---|
| committer | Nans Lefebvre <len@odoo.com> | 2019-06-12 11:31:16 +0000 |
| commit | 9ff767ec648bef997a3476117a64ceda75685843 (patch) | |
| tree | 0f71c35d5ffb1c25d968d48b9faec8756e63a1d1 /addons/web/static/src/js/fields/basic_fields.js | |
| parent | c41170ddc520c2eb44a882d113c4679392d5ad1c (diff) | |
[FIX] uom: fix nonempty reference constraint on uom categories
What's the deal with SQL queries?
The query in _check_category_reference_uniqueness returns:
category_id | uom_count
-------------+-----------
(0 rows)
but if we removed AND U.active = 't', we would have had:
category_id | uom_count
-------------+-----------
8 | 0
(1 row)
As a result, the check on uom_data['uom_count'] == 0 could simply never be true.
opw 1959679
closes odoo/odoo#32788
Signed-off-by: Nans Lefebvre (len) <len@odoo.com>
Diffstat (limited to 'addons/web/static/src/js/fields/basic_fields.js')
0 files changed, 0 insertions, 0 deletions