public inbox for [email protected]  

help / color / mirror / Atom feed

From: [email protected] <[email protected]>
To: [email protected]
Cc: Adrian Klaver <[email protected]>
Cc: David G. Johnston <[email protected]>
Subject: Re: Rules and Command Status - update/insert/delete rule with series of commands in action
Date: Thu, 30 May 2024 18:34:23 -0400
Message-ID: <PH0PR10MB695991BDE3588B549CE6A4D7A3F32@PH0PR10MB6959.namprd10.prod.outlook.com> (raw)
In-Reply-To: <[email protected]>
References: <PH0PR10MB6959209E2B0F36BE765E9159A3F32@PH0PR10MB6959.namprd10.prod.outlook.com>
	<[email protected]>


On 5/30/24 4:56 PM, David G. Johnston wrote:
>
> Very little interest exists in working on user-specified rules.  They 
> are practically deprecated.


Ah  -   pity  -   see my last comment to Adrian's


>
>     Any interest in perhaps providing a choice via a configuration
>     parameter?
>
>
>  If anything is done it would have to be new syntax.
>
>
A much bigger task surely.


On 5/30/24 5:19 PM, Adrian Klaver wrote:
>
> 2) Use INSTEAD OF triggers:
>
>

Unfortunately the same functionality as in my example with the RULE is 
not supported for triggers on views :   from the manual

|INSTEAD OF| triggers may only be defined on views, *and only at row level*;


A RULE is essentially a statement-level operation which is what I need 
for this particular case.      A row-level trigger would not work 
because it cannot "see" the query causing it to be fired, and also ,  
(most importantly) is not fired at all if no rows match the original 
query,     whereas a RULE is always in effect regardless of which rows 
are involved. before.      I should add that the RULE I showed in my 
example is not the only RULE being used on this view  -    there are 
other conditional RULEs,   and the combined effect is of being able to 
change the effect of the original statement into a set of new 
statements,   one of which does what is needed.


And if you are now inclined to say "well,    maybe the application 
itself is poorly written and should be changed"  -   I would have to 
agree,    but that is not mine to change.


But I suppose that my next question,   given what you both say about the 
RULE system being a dead-end,  is whether there is any likelihood of 
supporting an INSTEAD OF trigger on a view at statement level?   Maybe 
that stands more chance of going somewhere?



Cheers,     John Lumby

view thread (4+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Rules and Command Status - update/insert/delete rule with series of commands in action
  In-Reply-To: <PH0PR10MB695991BDE3588B549CE6A4D7A3F32@PH0PR10MB6959.namprd10.prod.outlook.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox