Page 1 of 1

System Update Issue

Posted: Thu Nov 08, 2018 1:09 am
by alf1976
Hi Steven,

I have an a problem with the system update. Whenever i run it it changes the database engine of all my tables from InnoDB back to MyISAM.

I use transaction statements on some of the tables. MyISAM is not a transaction engine.

At them moment i have run an sql statement to generate an ALTER TABLE list to convert them back. I leave all the 'zzzz' systems tables as MyISAM

Is there any reason why it alters the db engine of non system tables?

Andrew

Re: System Update Issue

Posted: Thu Nov 08, 2018 3:02 am
by admin
Andrew,

I have put a fix on Github.


Steven

Re: System Update Issue

Posted: Sat Nov 24, 2018 11:34 am
by alf1976
Hi Steven,

I have run a couple of system update off the last couple of fixes and all my tables are still being converted to MyISAM

After each update im having to run

Code: Select all

SELECT  CONCAT('ALTER TABLE `', table_name, '` ENGINE=InnoDB;') AS sql_statements
FROM    information_schema.tables AS tb
WHERE   table_schema = **MY DATABASE NAME**
AND     `ENGINE` = 'MyISAM'
AND     `TABLE_TYPE` = 'BASE TABLE'
AND 	TABLE_NAME NOT LIKE '%zzzz%'
to generate an sql statement to convert them all back




Andrew

Re: System Update Issue

Posted: Tue Nov 27, 2018 8:34 am
by Martin
Strange, this shouldn't happen. nuSetCollation included only tables starting with "zzzzsys"

Code: Select all

if(substr($tab, 0, 8) == 'zzzzsys_'){
https://github.com/nuSoftware/nuBuilder ... telibs.php

Re: System Update Issue

Posted: Thu Nov 29, 2018 10:31 pm
by alf1976
Hi

I've just down the latest pull from Github and ran the update. It hasn't done it on this pull.

Since Steven's post i havent paid much attention to the table structure and have done multiple updates since, so i'm not completely sure when this has happened.
I will monitor it from now on and if i have any more problems i will let you know

Andrew

Re: System Update Issue

Posted: Wed Dec 05, 2018 9:34 pm
by admin
.