On Thu, Jan 25, 2018 at 2:33 PM, David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Thu, Jan 25, 2018 at 3:06 PM, Ian Harding
> wrote:
>
>>
>> 4 |3 | Top.Bar.Blah
>> 5 |4 | Top.Bar.Blah.Scooby
>>
>>
>
>
>> barf$# UPDATE area SET areapath = (sele
On Thu, Jan 25, 2018 at 3:06 PM, Ian Harding wrote:
>
> 4 |3 | Top.Bar.Blah
> 5 |4 | Top.Bar.Blah.Scooby
>
>
> barf$# UPDATE area SET areapath = (select areapath from area a
> where areaid = area.parentid) || subpath(areapath, nlevel(areapath) - 1)
> b
On Thu, Jan 25, 2018 at 11:10 AM, David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Wednesday, January 24, 2018, Ian Harding wrote:
>
>>
>> -- This is not what I expect to see. I have even tried running the
>> update
>> -- unrestricted from within the trigger but I get the same result.
On Thu, Jan 25, 2018 at 10:51 AM, Adrian Klaver
wrote:
> On 01/24/2018 09:45 PM, Ian Harding wrote:
>
>> I have a conditional after update trigger on a table that issues an
>> update statement on the same table. The trigger does not fire recursively,
>> and I know the rows are being updated, but
On Wednesday, January 24, 2018, Ian Harding wrote:
>
> -- This is not what I expect to see. I have even tried running the update
> -- unrestricted from within the trigger but I get the same result. From
> -- outside the trigger I run the update unrestricted...
>
> UPDATE area SET areapath = (se
On 01/24/2018 09:45 PM, Ian Harding wrote:
I have a conditional after update trigger on a table that issues an
update statement on the same table. The trigger does not fire
recursively, and I know the rows are being updated, but the update is
not happening in the same way the statement does wh
I have a conditional after update trigger on a table that issues an update
statement on the same table. The trigger does not fire recursively, and I
know the rows are being updated, but the update is not happening in the
same way the statement does when run from outside the trigger.
--8<-
