| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Steve Crawford <scrawford(at)pinpointresearch(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: What does RIR as in fireRIRrules stand for? |
| Date: | 2015-08-28 14:20:58 |
| Message-ID: | 20551.1440771658@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2015-08-27 11:12:42 -0400, Tom Lane wrote:
>> I think an explanation in fireRIRrules' header comment would be fine.
> I was thinking of adding it to the file's header like
> * NOTES
> * Some of the terms used in this file are of historic nature: "retrieve"
> * was the PostQUEL keyword for what today is SELECT. "RIR" stands for
> * "Retrieve-Instead-Retrieve", that is an ON SELECT INSTEAD rule (which
> * has to be unconditional and where only one rule can exist on each
> * relation).
> since both retrieve and RIR are used in a bunch of places.
Seems reasonable. Maybe worth writing out the modern spelling a bit
further, "an ON SELECT DO INSTEAD SELECT rule", to make the parallel
to Retrieve-Instead-Retrieve perfectly clear.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nima Azizzadeh | 2015-08-28 14:29:25 | Define two factor authentication for Postgresql Server |
| Previous Message | Andres Freund | 2015-08-28 14:16:00 | Re: What does RIR as in fireRIRrules stand for? |