Browse Source

The 'disregarded' column wasn't set for existing entries, causing a DB error in some cases

Signed-off-by: Michael Eshom <[email protected]>
Michael Eshom 11 years ago
parent
commit
062f128403
3 changed files with 10 additions and 0 deletions
  1. 3 0
      other/upgrade_2-1_mysql.sql
  2. 3 0
      other/upgrade_2-1_postgresql.sql
  3. 4 0
      other/upgrade_2-1_sqlite.sql

+ 3 - 0
other/upgrade_2-1_mysql.sql

@@ -194,6 +194,9 @@ ADD COLUMN deny_member_groups varchar(255) NOT NULL DEFAULT '';
 ALTER TABLE {$db_prefix}log_topics
 ADD COLUMN disregarded tinyint(3) NOT NULL DEFAULT '0';
 
+UPDATE {$db_prefix}log_topics
+SET disregarded = 0;
+
 INSERT INTO {$db_prefix}settings
 	(variable, value)
 VALUES

+ 3 - 0
other/upgrade_2-1_postgresql.sql

@@ -253,6 +253,9 @@ upgrade_query("
 	ALTER TABLE {$db_prefix}log_topics
 	ADD COLUMN disregarded int NOT NULL DEFAULT '0'");
 
+UPDATE {$db_prefix}log_topics
+SET disregarded = 0;
+
 INSERT INTO {$db_prefix}settings
 	(variable, value)
 VALUES

+ 4 - 0
other/upgrade_2-1_sqlite.sql

@@ -236,6 +236,10 @@ $smcFunc['db_alter_table']('{db_prefix}log_topics', array(
 		),
 	)
 ));
+
+UPDATE {$db_prefix}log_topics
+SET disregarded = 0;
+
 INSERT INTO {$db_prefix}settings
 	(variable, value)
 VALUES