search

fusioninventory / fusioninventory-for-glpi

FusionInventory plugin for GLPI
http://www.FusionInventory.org/
GNU Affero General Public License v3.0
362 stars 150 forks source link

Create new tables using InnoDB #2826

Open marciofoz opened 5 years ago

marciofoz commented 5 years ago

Hi. I see that in new installs some tables use Memory engine. This tables will switch to the innodb engine ? I believe that this detail is missing in order to use the GLPI/Fusion in a mysql cluster database with the innodb mechanism.

Tables: glpi_plugin_fusioninventory_dblocksoftwareversions glpi_plugin_fusioninventory_dblocksoftwares glpi_plugin_fusioninventory_dblockinventorynames glpi_plugin_fusioninventory_dblockinventories

Script instal: fusioninventory-for-glpi/install/mysql/plugin_fusioninventory-empty.sql

BR

trasher commented 5 years ago

https://github.com/fusioninventory/fusioninventory-for-glpi/commit/465b520499174e29ce55d3ad1bd4de50dc8a0e01

marciofoz commented 5 years ago

Hi !!

I do not know why this issue was closed without any comment.

I keep seeing the script for creating the database tables using the memory engine. Must these tables use this engine ?

I ask it because for GLPI/Fusion to be 100% compatible with clustered database they should use primary keys with the InnoDB engine.

BR

trasher commented 5 years ago

I guess those tables are only required on inventory, no need to be replicated. Issue was closed because the switch to innodb has been done. ping @ddurieux

ddurieux commented 5 years ago

We use a non persistant table, because only used for locks when do inventory. So for performances, not write on disk and MEMORY engine is the best choice for this type of usage