Re: Re: Patch: Improve Boolean Predicate JSON Path Docs

From: Erik Wienhold <ewie(at)ewie(dot)name>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "David E(dot) Wheeler" <david(at)justatheory(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Re: Patch: Improve Boolean Predicate JSON Path Docs
Date: 2024-01-20 02:46:52
Message-ID: 6zxereqhl55sbpnevnh3szojc7w3dhowlb3fknzmi6mmwsi2q3@t3ubsz2gac5a
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2024-01-19 22:15 +0100, Tom Lane wrote:
> "David E. Wheeler" <david(at)justatheory(dot)com> writes:
> > [ v7-0001-Improve-boolean-predicate-JSON-Path-docs.patch ]
>
> + \set json '{
> "track": {
> "segments": [
> {
>
> I find the textual change rather unwieldy, but the bigger problem is
> that this example doesn't actually work. If you try to copy-and-paste
> this into psql, you get "unterminated quoted string", because psql
> metacommands can't span line boundaries.

Interesting... copy-pasting the entire \set command works for me with
psql 16.1 in gnome-terminal and tmux. Typing it out manually gives me
the "unterminated quoted string" error. Maybe has to do with my stty
settings.

> I experimented with
>
> SELECT '
> ... multiline json value ...
> ' AS json
> \gexec
>
> but that didn't seem to work either. Anybody have a better idea?

Fine with me (the \gset variant).

--
Erik

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2024-01-20 02:55:41 Re: add function argument names to regex* functions.
Previous Message vignesh C 2024-01-20 02:46:16 Re: Amcheck verification of GiST and GIN