Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.
--Table In question CREATE TABLE Cableroutings ( areacode TEXT( 4 ) NOT NULL, enc_class TEXT( 3 ) NOT NULL, enc_nbr INTEGER NOT NULL, prefix INTEGER NOT NULL, cabletype TEXT( 2 ) NOT NULL, suffix INTEGER NOT NULL, CONSTRAINT FKEY_Enclosures_Cablerouting FOREIGN KEY ( areacode, enc_class, enc_nbr ) REFERENCES Enclosures( areacode, enc_class, enc_nbr ) ON UPDATE CASCADE, CONSTRAINT FKEY_Cables_Cablerouting FOREIGN KEY ( prefix, cabletype, suffix ) REFERENCES Cables( prefix, cabletype, suffix ) ON UPDATE CASCADE ); --Access doesn't like CHECK constraints declared in Table Definition --But declaring them with ALTER TABLE ADD ... works just fine. ALTER TABLE Cableroutings ADD CONSTRAINT CHECK_ONLY_2_ROUTES_FOR_CABLE CHECK(( SELECT COUNT( * ) FROM Cableroutings AS CR WHERE CR.prefix = prefix AND CR.cabletype = cabletype AND CR.suffix = suffix ) BETWEEN 0 AND 2 );
Join the community of 500,000 technology professionals and ask your questions.
Connect with top rated Experts
18 Experts available now in Live!