Re: Variable substitution in psql backtick expansion

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: Variable substitution in psql backtick expansion
Дата
Msg-id CAKFQuwYp_tDbmrLShp_g-LtxpY7yv5GJ56ukjSgTCSq-W7U35w@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Variable substitution in psql backtick expansion  ("Daniel Verite" <daniel@manitou-mail.org>)
Список pgsql-hackers
On Mon, Apr 3, 2017 at 5:12 AM, Daniel Verite <daniel@manitou-mail.org> wrote:
Queries can be as complex as necessary, they just have to fit in one line.

​Line continuation in general is missed though I thought something already when in for 10.0 that improves upon this...​
 
In no way at all,in the sense that, either you choose to use an SQL
evaluator, or a client-side evaluator (if it exists), or a backtick
expression.
They are mutually exclusive for a single \if invocation.

Client-side evaluation would have to be called with a syntax
that is unambiguously different.

​Is that the universe: server, client, shell?

Shell already has backticks required
​Server, being the most common, ideally wouldn't need demarcation
Client thus would want its own symbol pairing to distinguish it from server.

Server doesn't need a leading marker but do we want to limit it to single statements only and allow an optional trailing semi-colon (or backslash command) which, if present, would end the "server" portion of the string and allow for treatment of additional terms on the same line to be parsed in a different context?

I'm conceptually for the implied "SELECT" idea.  It overlaps with plpgsql syntax.

David J.

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Stephen Frost
Дата:
Сообщение: Re: Rewriting the test of pg_upgrade as a TAP test
Следующее
От: "Jim Van Fleet"
Дата:
Сообщение: Re: Should we cacheline align PGXACT?