Error DB_ERROR_1072: ALTER TABLE llx_inventory ADD INDEX idx_inventory_tms (tms)

[PlanPc]

Bug

When updating from 5.0.4 to 6.0.0 get these 3 errors and proccess stops with a KO! .

I will thank any help to solve this, as I don´t know hot to solve without breaking it a little more... I´m stuck in the KO screen .

• Request 182 sql='ALTER TABLE llx_inventory ADD INDEX idx_inventory_tms (tms);'

• Error DB_ERROR_1072: ALTER TABLE llx_inventory ADD INDEX idx_inventory_tms (tms);Key column 'tms' doesn't exist in table

• Request 183 sql='ALTER TABLE llx_inventory ADD INDEX idx_inventory_datec (datec);' Request 184 sql='ALTER TABLE llx_inventorydet ADD INDEX idx_inventorydet_tms (tms);'

• Error DB_ERROR_1072: ALTER TABLE llx_inventorydet ADD INDEX idx_inventorydet_tms (tms);Key column 'tms' doesn't exist in table

• Request 185 sql='ALTER TABLE llx_inventorydet ADD INDEX idx_inventorydet_datec (datec);'

• Error DB_ERROR_1072: ALTER TABLE llx_inventorydet ADD INDEX idx_inventorydet_datec (datec);Key column 'datec' doesn't exist in table

Environment

• Version: 5.0.4 to 6.0.0 (update proccess)
• OS: Nginx (Dont know what version)
• Web server: Plesk (Dont know what version)
• PHP: 5.6.7

• Database: MySql 5.5.52-cll-lve

Expected and actual behavior

First time getting an error like that when updating Dolibarr, since V 3.

Steps to reproduce the behavior

Just update as always before, this time from 5.0.4 to 6.0.0

[Attached files - Heidi SQL screenshot of DB table]

[simnandez]

I can not reproduce the problem. Can you try updating to 6.0.5?

[PlanPc]

Thank you Juanjo for your quick answer.

Exact same result from 5.0.4 to 6.0.5.

Now, I try to update in order from actual 5.0.4 to:

5.0.5 -- OK 5.0.5 to 5.0.6 -- OK 5.0.6 to 5.0.7 -- OK 5.0.7 to 6.0.0 -- KO

Any idea?

[PlanPc]

Someone can indicate how to create those columns that Dolibarr has not automatically created in update proccess?

Cant find any reference to these tables or columns, in the Wiki, Changelog, Spanish, English and French forums, etc

Also there is no information about those tables, info seems outdated here: https://wiki.dolibarr.org/index.php/Category:Table_SQL

so dont know which are the parameters to create the columns manually, If I do not solve it at some point, I will drag the problem forever, as I will use Dolibarr at least till version 750.854.

Really don´t know where the problem comes from, but I supouse if it where from a third party module, the update script would never consider it for an ALTER TABLE in the update proccess, and if those tables / columns are from Dolibarr core modules, Why has been possible to bypass their creation at some point, if we are updating Dolibarr regularly?

Very confuse to me...

Regards

[github-actions[bot]]

This issue is stale because it has been open 1 year with no activity. If this is a bug, please comment to confirm it is still present on latest stable version. if this is a feature request, please comment to notify the request is still relevant and not yet covered by latest stable version. Without comment, this issue will be closed automatically by stale bot in 15 days.