- Fix unique constraint by using -1 instead of NULL for res_id
- Clean duplicate entries in po file
The unique constraint was not working when res_id was NULL because SQL consider
all of them as different.
The migration could fail if there is duplicate translation in the database. So
this query must be run until no more records are deleted:
DELETE FROM ir_translation WHERE id IN (SELECT MAX(id) FROM ir_translation GROUP BY name, res_id, lang, type, src_md5, module HAVING COUNT(1) > 1);
issue3355
review1087004
* Use python-sql
* Add convert_domain method on Fields
* Add sql_format and sql_type methods on Fields
* Allow to return a full domain for Function.searcher
* Replace static backend by dynamic get method
* Replace order_field by order_<field name> method
review1001002
- Remove the order on MPTT
- Make room with queries using left/right instead of ids
- Call _update_tree multiple times for small list instead of rebuild the all
tree
- Improve test for with many roots
- Factorize the test to update MPTT
issue1892
review1007002
SPLIT_PART is not a standard SQL function (it is not supported by MySQL).
SUBSTR is used even if it is not standard SQL because SUBSTRING is not
supported by SQLite. This will change once we will migrate to python-sql.
review784002
Importing records with m2o- and m2m-relations import_data gives record instances
to the create-method of the object instead of record-id's. Creating the same
object using the GUI the client gives record-id's.
On error the record-instances can't be serialized by JSON and the common error
"500 internal server error" will be reported to the client
issue3124
review767002
import_data method converts zero values to None. As a consequence such records
don't pass the required constraint for such fields
issue3136
review779002
It was introduced in changeset c7804c288ca3 but tools like proteus will set the
value on creation because there is a default value on such field as they are
required. So such test is not doable on creation.
issue3019