table name error => index llx_c_holiday_types not created with
Erreur DB_ERROR_1072 (Req 265): ALTER TABLE llx_c_holiday_types ADD UNIQUE INDEX uk_c_holiday_types (entity, code);
Key column 'entity' doesn't exist in table
* NEW : manage several type of dangerous goods for a same parcel
Manage several type of dangerous goods for a same parcel Before :
dangerous_goods : smallint (so only 1 type can be defined eg 3) After
dangerous_goods : varchar so can be a list of numbers eg 3,5,8
* Update llx_expedition_package.sql
> Adding a default value to default '0' to keep compatibility seems required.
* Update 20.0.0-21.0.0.sql
> You must include migration change into same PR so PR is atomic. Include change of #30237
* Update llx_expedition_package.sql
space missing
* Update 20.0.0-21.0.0.sql
> -- To change type of field: ALTER TABLE llx_table MODIFY COLUMN name varchar(60);
* replace old syntax
* replace old syntax
* replace old syntax
* replace old syntax
* rename files with same class name
* rename files with same class name
* rename files with same class name
* rename files with same class name
* rename files with same class name
* rename files with same class name
* rename files with same class name
* rename files with same class name
* rename files with same class name
* rename files with same class name
* rename files with same class name
* fix class with same name
* fix class with same name
* clean code
* Allow tweaking of the index that MySQL use when searching products
Sometimes when working with large dataset with many entities the MySQL engine does not pick-up the right index.
This is especially true when doing a search over the reference because the LIKE '%%' prevent the uk_product_label from being chosen.
This PR aims to improve this situation by doing the following :
- Adding a simple index on entity column.
- Adding an hidden constant to force the index being used when searching products.
Performances over a 8M products dataset shows a reduction of 2/3 execution time.
* Add missing global $conf
* Fix wrong usage of getDolGlobalString()
* Finalise fix
* Add more indexes
* Rework indexes
