Checking Data Boundaries And Trigger NotificationWhy doesn't INSERT AFTER Trigger add all results?Trigger in...

PTIJ: Aharon, King of Egypt

is 'sed' thread safe

Did Amazon pay $0 in taxes last year?

It doesn't matter the side you see it

Is there a full canon version of Tyrion's jackass/honeycomb joke?

Is there a frame of reference in which I was born before I was conceived?

Where is the fallacy here?

Practical reasons to have both a large police force and bounty hunting network?

Book about a time-travel war fought by computers

The need of reserving one's ability in job interviews

Is every open circuit a capacitor?

How do we objectively assess if a dialogue sounds unnatural or cringy?

When was drinking water recognized as crucial in marathon running?

PTIJ: Mordechai mourning

How does signal strength relate to bandwidth?

GDAL GetGeoTransform Documentation -- Is there an oversight, or what am I misunderstanding?

Deal the cards to the players

What can I do if someone tampers with my SSH public key?

I encountered my boss during an on-site interview at another company. Should I bring it up when seeing him next time?

Draw bounding region by list of points

Can the Shape Water Cantrip be used to manipulate blood?

Has Wakanda ever accepted refugees?

Can an earth elemental drown/bury its opponent underground using earth glide?

Where is this quote about overcoming the impossible said in "Interstellar"?



Checking Data Boundaries And Trigger Notification


Why doesn't INSERT AFTER Trigger add all results?Trigger in combination with transactionCreate Trigger MySql update or insert in another tableHow to commit transaction on an after update event trigger?Postgresql trigger update whole table after deleteTrigger on temp tablesql azure: trigger error when inserting into temp table from inserted tableProblems with insert trigger and primary keyPostgresql: Insert trigger function from select query, plus static values pulled from the new.<record>How to access data inside a “before insert trigger” for every statement













0















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!









share







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.

























    0















    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!









    share







    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.























      0












      0








      0








      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!









      share







      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





      share







      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.










      share







      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.








      share



      share






      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 5 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.






















          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.










          draft saved

          draft discarded


















          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.










          draft saved

          draft discarded


















          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.




          draft saved


          draft discarded














          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





















































          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







          Popular posts from this blog

          Anexo:Material bélico de la Fuerza Aérea de Chile Índice Aeronaves Defensa...

          Always On Availability groups resolving state after failover - Remote harden of transaction...

          update json value to null Announcing the arrival of Valued Associate #679: Cesar Manara ...