overrides

***OVERRIDES tables are bespoke for particular apps and not part of the pellucid master***

Summary

There are multiple override tables that link to different parent entity tables. Each provides record suppression information and whether or not the record should be suppressed from viewing for end users of public website, like the Illinois Report Card.  These tables are project specific and generally exist in shards of pellucid that power websites or projects.  The same overrides table can be different in two separate pellucid shards

Table Creation

DROP TABLE IF EXISTS `entity_astc_overrides`;

CREATE TABLE entity_astc_overrides ( 
`override_id` int(11) unsigned NOT NULL AUTO_INCREMENT, 
`entity_id` bigint(20) unsigned NOT NULL, 
`suppress` tinyint(1) DEFAULT '0', 
`entity_alias` tinyint(1) DEFAULT '0' 
`created` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00', 
`modified` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00' ON UPDATE CURRENT_TIMESTAMP, 
PRIMARY KEY (`override_id`), 
CONSTRAINT `entity_astc_overrides_ibfk_1` FOREIGN KEY (`entity_id`) REFERENCES `entity_astcs` (`entity_id`) ON DELETE CASCADE 
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

Field Information

`override_id` unique identifying number assigned to an override 
`entity_id` ID number that indicates an entity or asc. Links to the entity_hospitals or entity_ascs tables 
`suppress` Whether or not the entity should be suppressed from view. 1=Y 0=N 
`entity_alias` Whether or not the entity's alias is suppressed from view. 1=Y 0=N 
`created` the date and time the row was created in YYYY-MM-DD HH:MM:SS format 
`modified` the date and time the row was last edited in YYYY-MM-DD HH:MM:SS format

Fields

PRIMARY KEY (`override_id`) 
CONSTRAINT `entity_astc_overrides_ibfk_1` FOREIGN KEY (`entity_id`) REFERENCES `entity_astcs` (`entity_id`) ON DELETE CASCADE

Notes