<commit_before>-- KEN Core Data --

-- we are in a situation where KEN unit tests test against tables that are populated with bootstrap data
-- so we need to make sure that they are re-populated in tests, but that the repopulation doesn't lead to
-- constraint violations the first time around...so we pre-emptively delete beforehand
DELETE FROM NOTIFICATION_PRIORITIES /
DELETE FROM NOTIFICATION_CONTENT_TYPES /
DELETE FROM NOTIFICATION_PRODUCERS /

-- KEN Core Producers --
INSERT INTO NOTIFICATION_PRODUCERS
(ID, NAME, DESCRIPTION, CONTACT_INFO)
VALUES
(1, 'Notification System', 'This producer represents messages sent from the general message sending forms.', '<EMAIL>')
/

-- KEN Core Priorities --
INSERT INTO NOTIFICATION_PRIORITIES
(ID, NAME, DESCRIPTION, PRIORITY_ORDER)
VALUES
(1, 'Normal', 'Normal priority', 2)
/

INSERT INTO NOTIFICATION_PRIORITIES
(ID, NAME, DESCRIPTION, PRIORITY_ORDER)
VALUES
(2, 'Low', 'A low priority', 3)
/

INSERT INTO NOTIFICATION_PRIORITIES
(ID, NAME, DESCRIPTION, PRIORITY_ORDER)
VALUES
(3, 'High', 'A high priority', 1)
/

-- we are in a situation where KEN unit tests test against tables that are populated with bootstrap data<commit_msg>Fixed an issue with the KENBootstrap.sql file and it's delimiters<commit_after>-- KEN Core Data --

-- we are in a situation where KEN unit tests test against tables that are populated with bootstrap data
-- so we need to make sure that they are re-populated in tests, but that the repopulation doesn't lead to
-- constraint violations the first time around...so we pre-emptively delete beforehand
DELETE FROM NOTIFICATION_PRIORITIES
/
DELETE FROM NOTIFICATION_CONTENT_TYPES
/
DELETE FROM NOTIFICATION_PRODUCERS
/

-- KEN Core Producers --
INSERT INTO NOTIFICATION_PRODUCERS
(ID, NAME, DESCRIPTION, CONTACT_INFO)
VALUES
(1, 'Notification System', 'This producer represents messages sent from the general message sending forms.', '<EMAIL>')
/

-- KEN Core Priorities --
INSERT INTO NOTIFICATION_PRIORITIES
(ID, NAME, DESCRIPTION, PRIORITY_ORDER)
VALUES
(1, 'Normal', 'Normal priority', 2)
/

INSERT INTO NOTIFICATION_PRIORITIES
(ID, NAME, DESCRIPTION, PRIORITY_ORDER)
VALUES
(2, 'Low', 'A low priority', 3)
/

INSERT INTO NOTIFICATION_PRIORITIES
(ID, NAME, DESCRIPTION, PRIORITY_ORDER)
VALUES
(3, 'High', 'A high priority', 1)
/

-- we are in a situation where KEN unit tests test against tables that are populated with bootstrap data
{'fraction_non_alphanumeric': 0.0820215410107705, 'fraction_numerical': 0.00579950289975145, 'mean_word_length': 4.819277108433735, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '659804', 'n_tokens_mistral': 784, 'n_tokens_neox': 724, 'n_words': 304}