Project

General

Profile

« Previous | Next » 

Revision 10476

Added by Aaron Marcuse-Kubitza almost 11 years ago

bugfix: schemas/VegCore/VegCore.ERD.mwb: geovalidation: made scrubbed_geoplace optional because not all geoplaces will scrub to a valid geoplace

View differences:

VegCore.my.sql
261 261 
CREATE TABLE `geovalidation` (
262 262 
  `id` varbinary(767) NOT NULL,
263 263 
  `input_geoplace` varbinary(767) NOT NULL,
264 
  `scrubbed_geoplace` varbinary(767) NOT NULL,
264 
  `scrubbed_geoplace` varbinary(767) DEFAULT NULL,
265 265 
  `geovalid` tinyint(1) NOT NULL,
266 266 
  `lat_long_domain_valid` tinyint(1) NOT NULL,
267 267 
  `lat_long_in_place_ranks` set('hstore') COLLATE utf8_bin DEFAULT NULL,
268 268 
  PRIMARY KEY (`id`),
269 269 
  KEY `fk_geovalidation_geoplace1_idx` (`input_geoplace`),
270 270 
  KEY `fk_geovalidation_geoplace2_idx` (`scrubbed_geoplace`),
271 
  CONSTRAINT `fk_geovalidation_record1` FOREIGN KEY (`id`) REFERENCES `record` (`id`) ON DELETE CASCADE ON UPDATE CASCADE,
272 271 
  CONSTRAINT `fk_geovalidation_geoplace1` FOREIGN KEY (`input_geoplace`) REFERENCES `geoplace` (`id`) ON DELETE CASCADE ON UPDATE CASCADE,
273 
  CONSTRAINT `fk_geovalidation_geoplace2` FOREIGN KEY (`scrubbed_geoplace`) REFERENCES `geoplace` (`id`) ON DELETE CASCADE ON UPDATE CASCADE
272 
  CONSTRAINT `fk_geovalidation_geoplace2` FOREIGN KEY (`scrubbed_geoplace`) REFERENCES `geoplace` (`id`) ON DELETE CASCADE ON UPDATE CASCADE,
273 
  CONSTRAINT `fk_geovalidation_record1` FOREIGN KEY (`id`) REFERENCES `record` (`id`) ON DELETE CASCADE ON UPDATE CASCADE
274 274 
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='The accuracy of the [[VegCore#Coordinates|Coordinates]], taking into account the [[VegCore#Placename|Placename]]';
275 275 
/*!40101 SET character_set_client = @saved_cs_client */;
276 276 

  		












Also available in:  Unified diff