Forum GLPI-Project

hugo.matos

Member

Registered: 2022-06-20

Posts: 1

Table schema differs for table "glpi_states"

Hello all,

I recently update to 10.0.1 when finished I got:

"The database schema is not consistent with the current GLPI version. It is recommended to run the "php bin/console glpi:database:check_schema_integrity" command to see the differences"

when I do php bin/console glpi:database:check_schema_integrity I got:

Table schema differs for table "glpi_states".
--- Original
+++ New
@@ @@
   `entities_id` int NOT NULL DEFAULT 0,
   `is_recursive` tinyint NOT NULL DEFAULT 0,
   `is_visible_appliance` tinyint NOT NULL DEFAULT 1,
-  `is_visible_cable` tinyint NOT NULL DEFAULT 1,
   `is_visible_certificate` tinyint NOT NULL DEFAULT 1,
   `is_visible_cluster` tinyint NOT NULL DEFAULT 1,
   `is_visible_computer` tinyint NOT NULL DEFAULT 1,
@@ @@
   KEY `entities_id` (`entities_id`),
   KEY `is_recursive` (`is_recursive`),
   KEY `is_visible_appliance` (`is_visible_appliance`),
-  KEY `is_visible_cable` (`is_visible_cable`),
   KEY `is_visible_certificate` (`is_visible_certificate`),
   KEY `is_visible_cluster` (`is_visible_cluster`),
   KEY `is_visible_computer` (`is_visible_computer`),

bin/console glpi:database:update

Some optional system requirements are missing. Run "php bin/console glpi:system:check_requirements" for more details.
+-----------------------+-------------------------------------------------+-------------------------------------------------+
|                       | Current                                         | Target                                          |
+-----------------------+-------------------------------------------------+-------------------------------------------------+
| Database host         | localhost                                       |                                                 |
| Database name         | glpidb                                          |                                                 |
| Database user         | glpiadmin                                       |                                                 |
| GLPI version          | 10.0.1                                          | 10.0.1                                          |
| GLPI database version | 10.0.1@a130db99c7d9b131c2e2ea59fe0d6260fe93d831 | 10.0.1@a130db99c7d9b131c2e2ea59fe0d6260fe93d831 |
+-----------------------+-------------------------------------------------+-------------------------------------------------+
No migration needed.

How can I fix this?

lmonasterio

Member

From: Argentina

Registered: 2021-08-15

Posts: 6

Re: Table schema differs for table "glpi_states"

Hi. I have the same warning when updating to 10.0.2

Table schema differs for table "glpi_states".
--- Original
+++ New
@@ @@
   `entities_id` int NOT NULL DEFAULT 0,
   `is_recursive` tinyint NOT NULL DEFAULT 0,
   `is_visible_appliance` tinyint NOT NULL DEFAULT 1,
-  `is_visible_cable` tinyint NOT NULL DEFAULT 1,
   `is_visible_certificate` tinyint NOT NULL DEFAULT 1,
   `is_visible_cluster` tinyint NOT NULL DEFAULT 1,
   `is_visible_computer` tinyint NOT NULL DEFAULT 1,
@@ @@
   KEY `entities_id` (`entities_id`),
   KEY `is_recursive` (`is_recursive`),
   KEY `is_visible_appliance` (`is_visible_appliance`),
-  KEY `is_visible_cable` (`is_visible_cable`),
   KEY `is_visible_certificate` (`is_visible_certificate`),
   KEY `is_visible_cluster` (`is_visible_cluster`),
   KEY `is_visible_computer` (`is_visible_computer`),

wolvverinemp

Member

From: Poland

Registered: 2021-09-20

Posts: 31

Re: Table schema differs for table "glpi_states"

Upgrade from 10.0.0 to 10.0.2

# php bin/console glpi:database:check_schema_integrity
Schemat tabeli różni się dla tabeli "glpi_domains".
--- Original
+++ New
@@ @@
 CREATE TABLE `glpi_domains` (
   `id` int NOT NULL AUTO_INCREMENT,
   `comment` text,
-  `date_creation` datetime,
   `date_domaincreation` datetime,
   `date_expiration` datetime,
   `date_mod` datetime,
@@ @@
   `template_name` varchar(255),
   `users_id_tech` int NOT NULL DEFAULT 0,
   PRIMARY KEY (`id`),
-  KEY `date_creation` (`date_creation`),
-  KEY `date_domaincreation` (`date_domaincreation`),
   KEY `date_expiration` (`date_expiration`),
   KEY `date_mod` (`date_mod`),
   KEY `domaintypes_id` (`domaintypes_id`),
Schemat tabeli różni się dla tabeli "glpi_networkportethernets".
--- Original
+++ New
@@ @@
   `date_creation` datetime,
   `date_mod` datetime,
   `items_devicenetworkcards_id` int NOT NULL DEFAULT 0,
+  `netpoints_id` int NOT NULL DEFAULT 0,
   `networkports_id` int NOT NULL DEFAULT 0,
   `speed` int NOT NULL DEFAULT 10,
   `type` varchar(10) DEFAULT '',
@@ @@
   KEY `card` (`items_devicenetworkcards_id`),
   KEY `date_creation` (`date_creation`),
   KEY `date_mod` (`date_mod`),
+  KEY `netpoint` (`netpoints_id`),
   KEY `speed` (`speed`),
   KEY `type` (`type`)
 )
Schemat tabeli różni się dla tabeli "glpi_networkportfiberchannels".
--- Original
+++ New
@@ @@
   `date_creation` datetime,
   `date_mod` datetime,
   `items_devicenetworkcards_id` int NOT NULL DEFAULT 0,
+  `netpoints_id` int NOT NULL DEFAULT 0,
   `networkportfiberchanneltypes_id` int NOT NULL DEFAULT 0,
   `networkports_id` int NOT NULL DEFAULT 0,
   `speed` int NOT NULL DEFAULT 10,
@@ @@
   KEY `card` (`items_devicenetworkcards_id`),
   KEY `date_creation` (`date_creation`),
   KEY `date_mod` (`date_mod`),
+  KEY `netpoint` (`netpoints_id`),
   KEY `speed` (`speed`),
   KEY `type` (`networkportfiberchanneltypes_id`),
   KEY `wwn` (`wwn`)
)

Last edited by wolvverinemp (2022-07-05 18:33:05)

pchardnet

Member

Registered: 2010-06-10

Posts: 7

Re: Table schema differs for table "glpi_states"

More, and more

root@id18304:/home/suporte/public_html# php bin/console db:check_schema_integrity
O esquema da tabela difere da tabela "glpi_items_softwarelicenses".
--- Esquema de banco de dados esperado
+++ Esquema atual do banco de dados
@@ @@
   `itemtype` varchar(100) NOT NULL,
   `softwarelicenses_id` int NOT NULL DEFAULT 0,
   PRIMARY KEY (`id`),
+  KEY `computers_id` (`items_id`),
   KEY `is_deleted` (`is_deleted`),
   KEY `is_dynamic` (`is_dynamic`),
-  KEY `item` (`itemtype`,`items_id`),
   KEY `softwarelicenses_id` (`softwarelicenses_id`)
 )
O esquema da tabela difere da tabela "glpi_items_softwareversions".
--- Esquema de banco de dados esperado
+++ Esquema atual do banco de dados
@@ @@
   `itemtype` varchar(100) NOT NULL,
   `softwareversions_id` int NOT NULL DEFAULT 0,
   PRIMARY KEY (`id`),
-  UNIQUE KEY `unicity` (`itemtype`,`items_id`,`softwareversions_id`),
   KEY `computers_info` (`entities_id`,`is_template_item`,`is_deleted_item`),
   KEY `date_install` (`date_install`),
   KEY `is_deleted_item` (`is_deleted_item`),
O esquema da tabela difere da tabela "glpi_impactitems".
--- Esquema de banco de dados esperado
+++ Esquema atual do banco de dados
@@ @@
 CREATE TABLE `glpi_impactitems` (
   `id` int NOT NULL AUTO_INCREMENT,
-  `impactcontexts_id` int unsigned NOT NULL DEFAULT 0,
-  `is_slave` tinyint NOT NULL DEFAULT 1,
+  `depends_color` varchar(255) NOT NULL DEFAULT '',
+  `impact_and_depends_color` varchar(255) NOT NULL DEFAULT '',
+  `impact_color` varchar(255) NOT NULL DEFAULT '',
   `items_id` int NOT NULL DEFAULT 0,
   `itemtype` varchar(255) NOT NULL DEFAULT '',
+  `max_depth` int NOT NULL DEFAULT 5,
+  `pan_x` float NOT NULL DEFAULT 0,
+  `pan_y` float NOT NULL DEFAULT 0,
   `parent_id` int NOT NULL DEFAULT 0,
+  `position_x` float NOT NULL DEFAULT 0,
+  `position_y` float NOT NULL DEFAULT 0,
+  `show_depends` tinyint NOT NULL DEFAULT 1,
+  `show_impact` tinyint NOT NULL DEFAULT 1,
+  `zoom` float NOT NULL DEFAULT 0,
   PRIMARY KEY (`id`),
   UNIQUE KEY `unicity` (`itemtype`,`items_id`),
-  KEY `impactcontexts_id` (`impactcontexts_id`),
   KEY `parent_id` (`parent_id`),
   KEY `source` (`itemtype`,`items_id`)
 )