Forum GLPI-Project

kol123456

Member

Registered: 2020-01-09

Posts: 3

Table schema differs for table "glpi_budgets", "glpi_users".

Здравствуйте при попытке перехода с версии 9.5.7 до версии 10.0.6. Получаю предупреждение.

Table schema differs for table "glpi_budgets".
@@ @@
   KEY `budgettypes_id` (`budgettypes_id`),
   KEY `date_creation` (`date_creation`),
   KEY `date_mod` (`date_mod`),
-  KEY `end_date` (`end_date`),
   KEY `entities_id` (`entities_id`),
   KEY `is_deleted` (`is_deleted`),
   KEY `is_recursive` (`is_recursive`),

Table schema differs for table "glpi_users".
@@ @@
   UNIQUE KEY `unicityloginauth` (`name`,`authtype`,`auths_id`),
   KEY `authitem` (`authtype`,`auths_id`),
   KEY `auths_id` (`auths_id`),
-  KEY `begin_date` (`begin_date`),
   KEY `date_creation` (`date_creation`),
   KEY `date_mod` (`date_mod`),
   KEY `default_requesttypes_id` (`default_requesttypes_id`),
-  KEY `end_date` (`end_date`),
   KEY `entities_id` (`entities_id`),
   KEY `firstname` (`firstname`),
   KEY `groups_id` (`groups_id`),

Table schema differs for table "glpi_knowbaseitems".
@@ @@
   FULLTEXT KEY `answer` (`answer`),
   FULLTEXT KEY `fulltext` (`name`,`answer`),
   FULLTEXT KEY `name` (`name`),
-  KEY `begin_date` (`begin_date`),
   KEY `date_creation` (`date_creation`),
   KEY `date_mod` (`date_mod`),
-  KEY `end_date` (`end_date`),
   KEY `is_faq` (`is_faq`),
   KEY `users_id` (`users_id`)
)

Table schema differs for table "glpi_budgets".
Do you need to do something. And why did this happen at all, if I always installed and updated GLPI according to official instructions.

cconard96

Moderator

Registered: 2018-07-31

Posts: 2,813

Website

Re: Table schema differs for table "glpi_budgets", "glpi_users".

It is hard to say. The missing key for the budget table at least has existed as long as the table has in GLPI. It is possible it was missing from the SQL file for whichever version you initially installed GLPI from, or something else caused the key to be removed later.
You are only seeing this now because we added the ability to verify the database schema and added the message to have people check it. For others, it seems like updates can sometimes partially fail but look like they completed successfully and that led to missing fields or fields being left over/not migrated properly.
In this case, the missing keys shouldn't affect functionality but performance may be lower depending on the circumstance. You would have to re-add them in the database manually.

---

GLPI Collaborator and Plugin Developer.
My non-English comments are automated translations. Sorry for any confusion that causes.
Mes commentaires non anglais sont des traductions automatiques. Désolé pour toute confusion qui cause.
Mis comentarios que no están en inglés son traducciones automáticas. Perdón por cualquier confusión que cause.

cconard96

Moderator

Registered: 2018-07-31

Posts: 2,813

Website

Re: Table schema differs for table "glpi_budgets", "glpi_users".

Actually, it looks like that key had been set incorrectly in 0.78 and then later removed for a few versions, then re-added. It is likely that a migration was either bugged or had somehow failed and the keys weren't re-added properly.

---

GLPI Collaborator and Plugin Developer.
My non-English comments are automated translations. Sorry for any confusion that causes.
Mes commentaires non anglais sont des traductions automatiques. Désolé pour toute confusion qui cause.
Mis comentarios que no están en inglés son traducciones automáticas. Perdón por cualquier confusión que cause.

kol123456

Member

Registered: 2020-01-09

Posts: 3

Re: Table schema differs for table "glpi_budgets", "glpi_users".

Thank you. I installed a clean version with reliably correct tables, then corrected the inconsistent values in my working database. As a result, the check did not issue any warnings.