diff options
| author | Denis Ledoux <dle@odoo.com> | 2016-12-12 16:27:54 +0100 |
|---|---|---|
| committer | Denis Ledoux <dle@odoo.com> | 2016-12-12 18:18:51 +0100 |
| commit | 487c612f0ca45e48599b317b95acf19ba4f2dddd (patch) | |
| tree | 6419181f01019248ec105b48388454b8c29fc626 /addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js | |
| parent | 400a152b9131090a79de31f39d4eea3c349a36db (diff) | |
[FIX] web, orm: allow `0` as key for selection fields
Before this revision,
using a selection field with as possible keys `0`,
such as `require_payment` in `website_quote`,
resulted to the records field values to be stored
as `NULL` instead of `0` in the database.
This leads to the inability:
- To distinguish records with this selection field not set
or set to `0` (as both are stored as `NULL`)
- To search for records with the field set to `0`
(as they are considered not set)
For instance, while having `website_quote` installed,
search for sales orders with `Payment` set to
`Not mandatory on website quote validation`: It won't
return any result, even if you have some.
opw-697454
Diffstat (limited to 'addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js')
0 files changed, 0 insertions, 0 deletions
