SMF 2.0.18 has been released! Please update. Read more.
Started by Vekseid, February 16, 2009, 06:29:50 AM
Quote from: Arantor on September 18, 2013, 02:24:41 PMTry moving an individual board around, not just a whole category.It should also be noted that your database user really needs to have the ability to issue ALTER TABLE instructions, if this isn't an option it can mean it won't work properly.
Quote from: 青山 素子 on November 11, 2014, 02:06:50 PMXtraBackup works just fine with MySQL and MariaDB as well. Please note that the non-blocking backups are only for InnoDB and XtraDB tables. SMF sets up all tables as MyISAM for a new install. Unless you change the engine for the tables, you won't get the benefit of the tool.
Quote from: Kindred on November 11, 2014, 03:43:48 PMwell, in some cases, MyISAM is the correct type... regardless of what you "would prefer"...
Quote from: rjk on November 11, 2014, 02:30:56 PMI understand that some tables may be adversely affected by switching them to InnoDB. What can I do to prevent issues there, other than keeping MyISAM around? I would prefer to stick with InnoDB and MEMORY tables.
Quote from: Arantor on November 11, 2014, 03:57:28 PMTables with low write/high read uses, tables that need fulltext indexes will need MyISAM.
Quote from: 青山 素子 on November 11, 2014, 04:02:23 PMMemory tables are a bad idea for SMF as all tables it creates in the installer are expected to exist and persist data. Memory tables don't do that.
Quote from: 青山 素子 on November 11, 2014, 04:02:23 PMMy understanding is that InnoDB has improved enough to significantly reduce or remove the speed advantage MyISAM has/had in read operations.
QuoteOver 90% of all computer problems can be traced back to the interface between the keyboard and the chair