Issue 395 - Filter hits statistics backend

sitescripts/filterhits/schema.sql

 /*!40101 SET @saved_cs_client     = @@character_set_client */;
 /*!40101 SET character_set_client = utf8 */;
 CREATE TABLE `filters` (
-  `md5` BINARY(16) NOT NULL,
+  `sha1` BINARY(20) NOT NULL,
   `filter` TEXT CHARACTER SET utf8 NOT NULL,
-  PRIMARY KEY(md5)
+  PRIMARY KEY(sha1)
+) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin;
+
+CREATE TABLE `frequencies` (
+  `filter_sha1` BINARY(20) NOT NULL,
+  `domain` varchar(255) CHARACTER SET utf8 NOT NULL,
+  `frequency` int(10) unsigned DEFAULT 0 NOT NULL,
+  `timestamp` timestamp NOT NULL,
+  PRIMARY KEY(domain, filter_sha1)
 ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin;
 /*!40101 SET character_set_client = @saved_cs_client */;
-
-/*!40101 SET @saved_cs_client     = @@character_set_client */;
-/*!40101 SET character_set_client = utf8 */;

[Sebastian Noack, 2015/02/11 16:00:12]

This is redundant with the above. Not that we have to bother about setting the
client charset if we don't INSERT/UPDATE any text data.

[kzar, 2015/02/17 10:52:24]

Done.

[Sebastian Noack, 2015/02/17 14:59:17]

I just realized a typo in my comment above. I actually meant that as long as we
don't store any string data here, we don't have to bother about the client
charset. However, setting it won't hurt either way. And we're safe in case
things change in the future. But thanks for removing the code duplication.

-CREATE TABLE `geometrical_mean` (
-  `filter_md5` BINARY(16) NOT NULL,
-  `domain` varchar(255) CHARACTER SET utf8 NOT NULL,
-  `hits` int(10) unsigned DEFAULT 0 NOT NULL,
-  `timestamp` timestamp NOT NULL,
-  PRIMARY KEY(domain, filter_md5)
-) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin;
-/*!40101 SET character_set_client = @saved_cs_client */;