Added typo data collection (/submitData)

sitescripts/urlfixer/schema.sql

 DROP TABLE IF EXISTS domains;
 DROP TABLE IF EXISTS corrections;
 
 CREATE TABLE domains(
   id INT NOT NULL AUTO_INCREMENT,
   domain VARCHAR(50) NOT NULL,
-  domain_correct FLOAT(10,10),
-  correction_correct FLOAT(10,10),

[Wladimir Palant, 2012/10/09 11:51:14]

Aren't these two fields just derivatives of the data in corrections table? Then
we probably shouldn't cache them here for sake of database normalization -
better calculate them in the script used to extract the data later.

-  PRIMARY KEY(id)
+  PRIMARY KEY(id),
+  UNIQUE(domain)
 );
 
 CREATE TABLE corrections(
   id INT NOT NULL AUTO_INCREMENT,
   domain INT NOT NULL,
   status INT NOT NULL,
   curr_month INT NOT NULL,
   prev_month INT NOT NULL,
   curr_year INT NOT NULL,
   prev_year INT NOT NULL,
   PRIMARY KEY(id),
-  FOREIGN KEY(domain) REFERENCES domains(id)
+  FOREIGN KEY(domain) REFERENCES domains(id),
+  UNIQUE(domain, status)
 );
-
-CREATE UNIQUE INDEX idx_domain ON domains(domain);
-CREATE UNIQUE INDEX idx_domain_status ON corrections(domain, status);

[Wladimir Palant, 2012/10/09 11:51:14]

Use UNIQUE constraint instead of these two indexes? Meaning: UNIQUE (domains)
and UNIQUE (domain, status)

[Thomas Greiner, 2012/10/09 13:47:02]

I prefer having indexes because SELECTs on this table are made by using
domain+status and therefore it would speed up the process for the score
calculation and others.

[Wladimir Palant, 2012/10/09 14:17:08]

A UNIQUE constraint will always create an index implicitly.