JSON feedback

SQL/database_changelog.txt

@@ -1,15 +1,34 @@
 Any time you make a change to the schema files, remember to increment the database schema version. Generally increment the minor number, major should be reserved for significant changes to the schema. Both values go up to 255.
 
-The latest database version is 3.4; The query to update the schema revision table is:
+The latest database version is 4.0; The query to update the schema revision table is:
 
-INSERT INTO `schema_revision` (`major`, `minor`) VALUES (3, 4);
+INSERT INTO `schema_revision` (`major`, `minor`) VALUES (4, 0);
 or
-INSERT INTO `SS13_schema_revision` (`major`, `minor`) VALUES (3, 4);
+INSERT INTO `SS13_schema_revision` (`major`, `minor`) VALUES (4, 0);
 
 In any query remember to add a prefix to the table names if you use one.
 
 ----------------------------------------------------
 
+12 November 2017, by Jordie0608
+Modified feedback table to use json, a python script is used to migrate data to this new format.
+
+See the file 'feedback_conversion_2017-11-12.py' for instructions on how to use the script.
+
+A new json feedback table can be created with:
+CREATE TABLE `feedback` (
+  `id` int(11) unsigned NOT NULL AUTO_INCREMENT,
+  `datetime` datetime NOT NULL,
+  `round_id` int(11) unsigned NOT NULL,
+  `key_name` varchar(32) NOT NULL,
+  `key_type` enum('text', 'amount', 'tally', 'nested tally', 'associative') NOT NULL,
+  `version` tinyint(3) unsigned NOT NULL,
+  `json` json NOT NULL,
+  PRIMARY KEY (`id`)
+) ENGINE=MyISAM
+
+----------------------------------------------------
+
 28 August 2017, by MrStonedOne
 Modified table 'messages', adding a deleted column and editing all indexes to include it