Exclude constraint recreated when already existing

The new "exclude constraint" doesn't check if already existing, so it raise an 'already exists' error when running trytond-admin after creating a new "exclude constraint".

added trytond + 1 deleted label

Could you provide an example to reproduce?

added 1 deleted label and removed 1 deleted label

Example, first update to tip with
hg npull -u

then launch
trytond-admin -d xxx --all -v -c configfile
launch a second time trytond_admin, it raises an error
'psycopg2.ProgrammingError: relation "party_category_name_parent_exclude" already exists'
It's linked with the new exclude constraint in https://codereview.tryton.org/35981002/

The exclude constraint creation should have a 'IF NOT EXISTS' (don't know if it is possible)

Indeed the problem is in TableHandler._update_definitions which does not fill the _constraints with the exclude constraint.
It seems that the table information_schema.table_constraints does not contain exclude constraint.

assigned to @ced

added type::crash + 1 deleted label and removed 1 deleted label

Indeed PostgreSQL explicitly ignore exclude constraint from the view: https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/backend/catalog/information_schema.sql;h=f4e69f4a264c4c68d18425eb16090703e956dccc;hb=HEAD#l1796

added 1 deleted label and removed 1 deleted label

review37121002 updated at https://codereview.tryton.org/37121002/#ps1

New changeset 92ef962bcd69 by Cédric Krier in branch 'default':
Add non-standard exclude constraint in TableHandler definition
http://hg.tryton.org/trytond/rev/92ef962bcd69

added 1 deleted label and removed 1 deleted label

closed