Changes to the MySQL schema to be more like jfbethlehem's SQLite schema.

An update2.sql is provided that might update the schema without data loss,
however if you value your data, it's a good idea to create a backup first.



git-svn-id: https://kippo.googlecode.com/svn/trunk@127 951d7100-d841-11de-b865-b3884708a8e2

doc/sql/update2.sql

@@ -0,0 +1,30 @@
+--
+-- WARNING: Existing data may be lost & messed up
+--
+
+ALTER TABLE `session` RENAME `sessions` ;
+
+CREATE TABLE IF NOT EXISTS `sensors` (
+  `id` int(11) NOT NULL auto_increment,
+  `ip` varchar(15) NOT NULL,
+  PRIMARY KEY  (`id`)
+) ;
+
+INSERT INTO `sensors` (`ip`) (SELECT DISTINCT `sensor` FROM `sessions`) ;
+
+UPDATE `sessions` SET `sensor` =
+    (SELECT `id` FROM `sensors` WHERE `sensors`.`ip` = `sessions`.`sensor`) ;
+
+ALTER TABLE `sessions` CHANGE `sensor` `sensor` INT( 4 ) NOT NULL ;
+
+CREATE TABLE IF NOT EXISTS `ttylog` (
+  `id` int(11) NOT NULL auto_increment,
+  `session` int(11) NOT NULL,
+  `ttylog` mediumblob NOT NULL,
+  PRIMARY KEY  (`id`)
+) ;
+
+INSERT INTO `ttylog` (`session`, `ttylog`)
+    (SELECT `id`, `ttylog` FROM `sessions` WHERE LENGTH(`ttylog`) > 0) ;
+
+ALTER TABLE `sessions` DROP `ttylog` ;