| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Undefined psql variables |
| Date: | 2017-01-23 20:57:17 |
| Message-ID: | alpine.DEB.2.20.1701232152080.31421@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Back in the day, PG allowed ":" as a generic operator name, making
> this even worse; but I think the only remaining SQL syntax that could
> include a colon is array slicing.
Ok, so the behavior of replacing ":unknown" by same cannot be changed.
Some fun:
\set 1 1
SELECT ('{1,2,3,4,5,6,7,8,9,10,11,12}'::INT[])[1:1];
-- yields 11
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2017-01-23 20:59:32 | Re: PoC plpgsql - possibility to force custom or generic plan |
| Previous Message | Fabien COELHO | 2017-01-23 20:43:09 | Re: Allowing nonzero return codes from \quit |