|From:||Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>|
|To:||Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>|
|Cc:||Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Undefined psql variables|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
> you proposal disallow client side expressions.
I do agree that some client side expressions are necessary. I do not want
to disallow them.
> I agree so is not possible to mix server side and client side
My point is that a minimal of cross-support is possible.
> But I am sceptic so benefit of server side expression is higher than a
> lost of client side expressions.
There is a misunderstanding. I am not against client side expression. I do
want to allow the same server & client side capabilities suggested by Tom,
I'm just arguing about the syntax, to avoid a prefix oriented approach.
> If we disallow server side expressions, then your examples are only two
> lines longer, but the implementation can be more simpler.
> SELECT version FROM app_version
> \if :version >= 2.0
> Still I don't think so server side expression in \if is good idea.
Ok, so you do not like server-side expression capabities integrated to
\if. I understood that you were in favor of Tom's proposal.
From a semantical point of view they are not necessary because the same
effect can be obtained through \gset, at the price of an intermediate
variable. So the server-side thing is just a syntax convenience. I think
that independently of whether they are added, Tom's point is that it
should be possible to add those features later on, hence the discussion
about a design.
|Next Message||Fabien COELHO||2017-04-08 10:33:15||Re: [HACKERS] Small issue in online devel documentation build|
|Previous Message||Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?=||2017-04-08 09:43:13||Re: [PATCH] Add GUCs for predicate lock promotion thresholds|