Hi Tom,
Ok, thanks.
On Tue, Jun 20, 2017 at 3:21 PM, Tom Lane wrote:
> Osahon Oduware writes:
> > The pg_trigger_depth() function solved the issue. Thanks a lot, you made
> my
> > day.
>
> If you start finding that that gets in your way for other purposes, you
> might try making table A's trig
Osahon Oduware writes:
> The pg_trigger_depth() function solved the issue. Thanks a lot, you made my
> day.
If you start finding that that gets in your way for other purposes, you
might try making table A's trigger function be SECURITY DEFINER and
owned by a role that has permissions to change ta
Hi Achilleas,
The pg_trigger_depth() function solved the issue. Thanks a lot, you made my
day.
On Tue, Jun 20, 2017 at 12:58 PM, Achilleas Mantzios <
ach...@matrix.gatewaynet.com> wrote:
> On 20/06/2017 14:43, Osahon Oduware wrote:
>
> Hi All,
>
> I have a trigger on a PostGIS table (say table A
On 20/06/2017 14:43, Osahon Oduware wrote:
Hi All,
I have a trigger on a PostGIS table (say table A) that automatically updates another PostGIS table (say table B). Also, users connect to these tables (table A and B) using QGIS. However, I want the
updates to table B to be done by the trigger o
Hi All,
I have a trigger on a PostGIS table (say table A) that automatically
updates another PostGIS table (say table B). Also, users connect to these
tables (table A and B) using QGIS. However, I want the updates to table B
to be done by the trigger only (i.e. I don't want table B to be updated
f
