Checking Data Boundaries And Trigger Notification
I'm creating backend that send notification if inserted data exceed expected value.
I have 3 (simple structure) tables:
bigFatData table:
id,locId,temp,moistLevel,salRange,insertedDate
fencing table:
id,locId,fencingFld,fencingVal,insertedDate
notifications table:
id,locId,msg,insertedDate
So for example if there's a record in fencing table:
12,101,'temp',55.20,2019-03-07 10:50:54.200294+07
and one of our sensor tries to insert something to bigFatTable, like:
101,56.00,15,100,NOW()
it will trigger another insert to notifications table, like:
101,concat('Warning! Data: ', fencingFld, ' exceeds value: ',
fencingVal), NOW()
Right now, I'm creating ugly IF EXISTS check in trigger like this:
CREATE OR REPLACE FUNCTION checkDataFencingFunction() RETURNS TRIGGER AS
$$
BEGIN
IF EXISTS (SELECT locId,fencingFld,fencingVal FROM fencing WHERE locId = NEW.locID AND fencingFld = 'temp' AND fencingFld < NEW.temp::double precision) THEN
INSERT INTO data.notifications(locId, msg) VALUES (NEW.locID, 'Warning! Data exceeds!');
END IF;
IF EXISTS (SELECT locId,fencingFld,fencingVal FROM fencing WHERE locId = NEW.locID AND fencingFld = 'moistLevel' AND fencingFld < NEW.moistLevel::double precision) THEN
INSERT INTO data.notifications(locId, msg) VALUES (NEW.locID, 'Warning! Data exceeds!');
END IF;
IF EXISTS (SELECT locId,fencingFld,fencingVal FROM fencing WHERE locId = NEW.locID AND fencingFld = 'salRange' AND fencingFld < NEW.salRange::double precision) THEN
INSERT INTO data.notifications(locId, msg) VALUES (NEW.locID, 'Warning! Data exceeds!');
END IF;
END;
$$
language plpgsql;
CREATE TRIGGER checkDataFencingTrigger
AFTER INSERT ON bigFatData
FOR EACH ROW
EXECUTE PROCEDURE checkDataFencingFunction();
I believe there's a better way than putting tons of IF EXISTS check in the function. Any suggestions?
Thanks!
postgresql trigger
asked 11 mins ago
SanShinSanShin
1
New contributor
SanShin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I'm creating backend that send notification if inserted data exceed expected value.
I have 3 (simple structure) tables:
bigFatData table:
id,locId,temp,moistLevel,salRange,insertedDate
fencing table:
id,locId,fencingFld,fencingVal,insertedDate
notifications table:
id,locId,msg,insertedDate
So for example if there's a record in fencing table:
12,101,'temp',55.20,2019-03-07 10:50:54.200294+07
and one of our sensor tries to insert something to bigFatTable, like:
101,56.00,15,100,NOW()
it will trigger another insert to notifications table, like:
101,concat('Warning! Data: ', fencingFld, ' exceeds value: ',
fencingVal), NOW()
Right now, I'm creating ugly IF EXISTS check in trigger like this:
CREATE OR REPLACE FUNCTION checkDataFencingFunction() RETURNS TRIGGER AS
$$
BEGIN
IF EXISTS (SELECT locId,fencingFld,fencingVal FROM fencing WHERE locId = NEW.locID AND fencingFld = 'temp' AND fencingFld < NEW.temp::double precision) THEN
INSERT INTO data.notifications(locId, msg) VALUES (NEW.locID, 'Warning! Data exceeds!');
END IF;
IF EXISTS (SELECT locId,fencingFld,fencingVal FROM fencing WHERE locId = NEW.locID AND fencingFld = 'moistLevel' AND fencingFld < NEW.moistLevel::double precision) THEN
INSERT INTO data.notifications(locId, msg) VALUES (NEW.locID, 'Warning! Data exceeds!');
END IF;
IF EXISTS (SELECT locId,fencingFld,fencingVal FROM fencing WHERE locId = NEW.locID AND fencingFld = 'salRange' AND fencingFld < NEW.salRange::double precision) THEN
INSERT INTO data.notifications(locId, msg) VALUES (NEW.locID, 'Warning! Data exceeds!');
END IF;
END;
$$
language plpgsql;
CREATE TRIGGER checkDataFencingTrigger
AFTER INSERT ON bigFatData
FOR EACH ROW
EXECUTE PROCEDURE checkDataFencingFunction();
I believe there's a better way than putting tons of IF EXISTS check in the function. Any suggestions?
Thanks!
postgresql trigger
asked 11 mins ago
SanShinSanShin
1
New contributor
SanShin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I'm creating backend that send notification if inserted data exceed expected value.
I have 3 (simple structure) tables:
bigFatData table:
id,locId,temp,moistLevel,salRange,insertedDate
fencing table:
id,locId,fencingFld,fencingVal,insertedDate
notifications table:
id,locId,msg,insertedDate
So for example if there's a record in fencing table:
12,101,'temp',55.20,2019-03-07 10:50:54.200294+07
and one of our sensor tries to insert something to bigFatTable, like:
101,56.00,15,100,NOW()
it will trigger another insert to notifications table, like:
101,concat('Warning! Data: ', fencingFld, ' exceeds value: ',
fencingVal), NOW()
Right now, I'm creating ugly IF EXISTS check in trigger like this:
CREATE OR REPLACE FUNCTION checkDataFencingFunction() RETURNS TRIGGER AS
$$
BEGIN
IF EXISTS (SELECT locId,fencingFld,fencingVal FROM fencing WHERE locId = NEW.locID AND fencingFld = 'temp' AND fencingFld < NEW.temp::double precision) THEN
INSERT INTO data.notifications(locId, msg) VALUES (NEW.locID, 'Warning! Data exceeds!');
END IF;
IF EXISTS (SELECT locId,fencingFld,fencingVal FROM fencing WHERE locId = NEW.locID AND fencingFld = 'moistLevel' AND fencingFld < NEW.moistLevel::double precision) THEN
INSERT INTO data.notifications(locId, msg) VALUES (NEW.locID, 'Warning! Data exceeds!');
END IF;
IF EXISTS (SELECT locId,fencingFld,fencingVal FROM fencing WHERE locId = NEW.locID AND fencingFld = 'salRange' AND fencingFld < NEW.salRange::double precision) THEN
INSERT INTO data.notifications(locId, msg) VALUES (NEW.locID, 'Warning! Data exceeds!');
END IF;
END;
$$
language plpgsql;
CREATE TRIGGER checkDataFencingTrigger
AFTER INSERT ON bigFatData
FOR EACH ROW
EXECUTE PROCEDURE checkDataFencingFunction();
I believe there's a better way than putting tons of IF EXISTS check in the function. Any suggestions?
Thanks!
postgresql trigger
asked 11 mins ago
SanShinSanShin
1
New contributor
SanShin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I'm creating backend that send notification if inserted data exceed expected value.
I have 3 (simple structure) tables:
bigFatData table:
id,locId,temp,moistLevel,salRange,insertedDate
fencing table:
id,locId,fencingFld,fencingVal,insertedDate
notifications table:
id,locId,msg,insertedDate
So for example if there's a record in fencing table:
12,101,'temp',55.20,2019-03-07 10:50:54.200294+07
and one of our sensor tries to insert something to bigFatTable, like:
101,56.00,15,100,NOW()
it will trigger another insert to notifications table, like:
101,concat('Warning! Data: ', fencingFld, ' exceeds value: ',
fencingVal), NOW()
Right now, I'm creating ugly IF EXISTS check in trigger like this:
CREATE OR REPLACE FUNCTION checkDataFencingFunction() RETURNS TRIGGER AS
$$
BEGIN
IF EXISTS (SELECT locId,fencingFld,fencingVal FROM fencing WHERE locId = NEW.locID AND fencingFld = 'temp' AND fencingFld < NEW.temp::double precision) THEN
INSERT INTO data.notifications(locId, msg) VALUES (NEW.locID, 'Warning! Data exceeds!');
END IF;
IF EXISTS (SELECT locId,fencingFld,fencingVal FROM fencing WHERE locId = NEW.locID AND fencingFld = 'moistLevel' AND fencingFld < NEW.moistLevel::double precision) THEN
INSERT INTO data.notifications(locId, msg) VALUES (NEW.locID, 'Warning! Data exceeds!');
END IF;
IF EXISTS (SELECT locId,fencingFld,fencingVal FROM fencing WHERE locId = NEW.locID AND fencingFld = 'salRange' AND fencingFld < NEW.salRange::double precision) THEN
INSERT INTO data.notifications(locId, msg) VALUES (NEW.locID, 'Warning! Data exceeds!');
END IF;
END;
$$
language plpgsql;
CREATE TRIGGER checkDataFencingTrigger
AFTER INSERT ON bigFatData
FOR EACH ROW
EXECUTE PROCEDURE checkDataFencingFunction();
I believe there's a better way than putting tons of IF EXISTS check in the function. Any suggestions?
Thanks!
postgresql trigger
postgresql trigger
asked 11 mins ago
SanShinSanShin
1
New contributor
SanShin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 11 mins ago
SanShinSanShin
1
New contributor
SanShin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 11 mins ago
SanShinSanShin
1
New contributor
SanShin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 11 mins ago
SanShinSanShin
1
asked 11 mins ago
SanShinSanShin
1
1
New contributor
SanShin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
SanShin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
SanShin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
SanShin is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f231514%2fchecking-data-boundaries-and-trigger-notification%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
SanShin is a new contributor. Be nice, and check out our Code of Conduct.
SanShin is a new contributor. Be nice, and check out our Code of Conduct.
SanShin is a new contributor. Be nice, and check out our Code of Conduct.
SanShin is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f231514%2fchecking-data-boundaries-and-trigger-notification%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
