Cédric Krier 83656053c8 Order operation on relational field to avoid constraints ...

The order on which the operations are applied can trigger constraints.
So it is safer to first delete then write and finally create.

issue6790
review43511002

2017-09-28 23:44:48 +02:00

..

__init__.py

Add MultiValueMixin and ValueMixin and remove Propery

2017-04-01 00:24:55 +02:00

binary.py

Move low level handling of the SQL type to the backend

2017-03-31 12:44:22 +02:00

boolean.py

Move low level handling of the SQL type to the backend

2017-03-31 12:44:22 +02:00

char.py

Move low level handling of the SQL type to the backend

2017-03-31 12:44:22 +02:00

date.py

Move low level handling of the SQL type to the backend

2017-03-31 12:44:22 +02:00

dict.py

Only convert dict fields when they are strings

2017-06-09 13:22:42 +02:00

field.py

Ensure all _parent_ values are set on fields.depends

2017-04-26 13:56:30 +02:00

float.py

Move low level handling of the SQL type to the backend

2017-03-31 12:44:22 +02:00

function.py

Use _field for sql_format of Function field

2017-04-01 19:55:35 +02:00

integer.py

Move low level handling of the SQL type to the backend

2017-03-31 12:44:22 +02:00

many2many.py

Order operation on relational field to avoid constraints

2017-09-28 23:44:48 +02:00

many2one.py

Ensure Many2One target join is unique if Target has history

2017-04-26 19:33:32 +02:00

numeric.py

Move low level handling of the SQL type to the backend

2017-03-31 12:44:22 +02:00

one2many.py

Order operation on relational field to avoid constraints

2017-09-28 23:44:48 +02:00

one2one.py

Order operation on relational field to avoid constraints

2017-09-28 23:44:48 +02:00

reference.py

Add translated descriptor for Reference field

2017-09-26 01:25:26 +02:00

selection.py

Add translated descriptor for Reference field

2017-09-26 01:25:26 +02:00

text.py

Move low level handling of the SQL type to the backend

2017-03-31 12:44:22 +02:00