Re: PL/pgSQL 1.2

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Hannu Krosing <hannu(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Joel Jacobson <joel(at)trustly(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PL/pgSQL 1.2
Date: 2014-09-06 09:12:43
Message-ID: 540AD00B.7040205@joh.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

(Forgot to answer to this part)

On 2014-09-06 06:59, Pavel Stehule wrote:
> Your strategy is defensive. 100%. But then I don't understand to your
> resistant to verbosity. It is one basic stone of Ada design

I've never programmed in Ada, but I don't necessarily see why "more
verbose" would unconditionally mean "more defensive".

My primary reason for objecting to some of the syntax suggestions that
have been thrown around previously and during the last couple of days is
that once you increase verbosity enough, the specialized syntax starts
to be less and less desirable compared to what you can already do today.
And even that I only try to apply to the parts of the syntax I find
verbose just for the sake of being verbose, i.e. without any additional
functionality, disambiguity or clarity. For example, having something
like a CONSTRAINT CHECK (row_count = 1); is not really significantly
better than RETURNING TRUE INTO STRICT _OK. It's better because the
intent is more clear, and because you don't need a special _OK variable,
but it still has 90% of the pain of the syntax you can use today. That
being the useless verbosity.

.marko

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2014-09-06 10:40:00 Re: SKIP LOCKED DATA (work in progress)
Previous Message Zhaomo Yang 2014-09-06 08:24:16 Re: A mechanism securing web applications in DBMS