diff options
| author | Nicolas Seinlet <nse@openerp.com> | 2018-09-18 11:06:43 +0200 |
|---|---|---|
| committer | Nicolas Seinlet <nse@openerp.com> | 2018-09-20 13:25:28 +0200 |
| commit | b5a12b4aac9484cd342e29f2a0402fb148b09e2e (patch) | |
| tree | 1eeb9bf379a313e32c04ee2b09e611b8f5ff1096 /addons/web/static/src/xml/pie_chart.xml | |
| parent | e7c53bd15075b7cf1124f9ea03d08e608c495603 (diff) | |
[IMP] website: ensure login uniqueness per website in SQL
Constraints in SQL are faster than python equivalent.
Adding a coalesce in PostgreSQL constraint doesn't seems possible.
This combination of constraint and weird named unique index is the
fastest way to ensure a unique constraint with NULL values.
This index require the website_id to be present in the res_users
table. To do this, a stored readonly related field is used.
This was introduced by 4f6ec1cd2a9253bb0c6c17d304490c7809facf8a
Diffstat (limited to 'addons/web/static/src/xml/pie_chart.xml')
0 files changed, 0 insertions, 0 deletions