Implement database migrations about munkireport-php HOT 2 CLOSED

I renamed your issue, we need to seriously think about database migrations. The easiest way is to drop the table and let munkireport recreate it, but that may mean that you lose data (from machines that don't report very often).

The issue at hand is that I changed the physical_memory column from VARCHAR to INT. To accommodate this change in initialised databases, you'll have to change the column definition.

In MySQL you could run:

START TRANSACTION;
UPDATE machine SET physical_memory = SUBSTRING_INDEX(physical_memory, ' ', 1);
ALTER TABLE machine MODIFY physical_memory INT;
COMMIT;

For SQLite it is a little more daunting, because SQLite does not support altering a column type. So we would have to create a temporary table, copy the current table, drop the current table, create the new table, copy the data to the new table and drop the temporary table.

from munkireport-php.

Resolved with dc8d287

from munkireport-php.