[FIX] models: behavior with multiple inverse/compute mixed on same fields

1 files changed, 1 insertions, 7 deletions

diff --git a/addons/base_address_extended/models/base_address_extended.py b/addons/base_address_extended/models/base_address_extended.py
index a2c31249951..1ca0178ba20 100644
--- a/addons/base_address_extended/models/base_address_extended.py
+++ b/addons/base_address_extended/models/base_address_extended.py
@@ -74,12 +74,7 @@ class Partner(models.Model):
 
             # add trailing chars in street_format
             street_value += street_format[previous_pos:]
-
-            # /!\ Note that we must use a sql query to bypass the orm as it would call _split_street()
-            # that would try to set the fields we just modified.
-            self._cr.execute('UPDATE res_partner SET street = %s WHERE ID = %s', (street_value, partner.id))
-            #invalidate the cache for the field we manually set
-            self.invalidate_cache(['street'], [partner.id])
+            partner.street = street_value
 
     @api.multi
     @api.depends('street')
@@ -133,7 +128,6 @@ class Partner(models.Model):
             else:
                 vals[field_name] = street_raw
             # assign the values to the fields
-            # /!\ Note that a write(vals) would cause a recursion since it would bypass the cache
             for k, v in vals.items():
                 partner[k] = v