Feedback-ID: ia2694551:Fastmail
Date: Thu, 22 Sep 2022 16:10:35 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Guillaume Lelarge <guillaume@lelarge.info>
Cc: SAS <sas.postgresql@gmail.com>, pgsql-translators@postgresql.org
Subject: Re: French translation mistake
Message-ID: <20220922141035.3z6tu4nqg2vrmogt@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAECtzeXu7Cr9xmVoZbqc1O9z1qa32tMZB9RP0MMM-06e-Zj=bA@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/20220922141035.3z6tu4nqg2vrmogt%40alvherre.pgsql>
Precedence: bulk

On 2022-Sep-22, Guillaume Lelarge wrote:

> Le jeu. 22 sept. 2022 à 10:59, SAS <sas.postgresql@gmail.com> a écrit :

> > Reading xproc.html for PG14, in both french and english, I wonder if
> > french translation is totally accurate.
> >
> > The english version says :
> > Certain function attributes, such as strictness, don't apply to
> > procedures. Those attributes control how the function is used in a query,
> > which isn't relevant to procedures.

> I'd like to know this as well, so that I could fix it if need be.

Well, volatility and strictness are different things.  However, you
cannot set either of them for procedures, so while this is technically
not an accurate translation, in practice it makes no difference.

create procedure f (a int) language plpgsql strict as $$ begin raise notice 'called once'; end $$;
ERROR:  invalid attribute in procedure definition
LÍNEA 1: create procedure f (a int) language plpgsql strict as $$ beg...
                                                     ^


-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"Right now the sectors on the hard disk run clockwise, but I heard a rumor that
you can squeeze 0.2% more throughput by running them counterclockwise.
It's worth the effort. Recommended."  (Gerry Pourwelle)