Rules and decision logic triggered by / acting on JSONB nodes in Postgres

From: Amit Kothari <amit(at)tallyfy(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Rules and decision logic triggered by / acting on JSONB nodes in Postgres
Date: 2018-09-01 14:14:00
Message-ID: 20108283-DE54-4754-8371-B34547BE0739@tallyfy.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi all,

I’m sorry if this question is off-topic for postgres-core, but didn’t know where else to ask.

We’ve built a workflow and BPM (business process management) tool with pg as the database, and we’d like to explore conditional logic within steps in a workflow being triggers as functions when a certain JSONB node changes.

An example -> If (form field contains “bob”) then (change state of another object)

In effect, since all our objects are JSONB - we wanted to “listen” to a change in one JSONB node in order to make a corresponding change in another JSONB node.

Can this be either native in postgres, or even a pg function?

In general - how do people approach rules and decision logic in Postgres at a very large scale e.g. say 100,000 rules that must be evaluated on a commit?

If it makes more sense - please see the example screenshot on our features page at https://tallyfy.com/features - which visualizes conditional branching.

Thanks,
Amit
https://tallyfy.com

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Olivier Leprêtre 2018-09-01 15:50:31 TR: redundant constraint_schema
Previous Message Dave Peticolas 2018-09-01 03:48:04 Re: locate DB corruption