| From: | "Joel Jacobson" <joel(at)compiler(dot)org> |
|---|---|
| To: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Schema variables - new implementation for Postgres 15 |
| Date: | 2022-01-13 17:00:40 |
| Message-ID: | 1ebeaf57-da83-42e1-9302-fb126281814d@www.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 13, 2022, at 20:12, Pavel Stehule wrote:
>I cannot imagine how the "window" keyword can work in SQL context. In Javascript "window" is an object - it is not a keyword, and it makes sense in usual Javascript context inside HTML browsers.
I was thinking since Javascript is by far the most known programming language, the "window" word would be familiar and easy to remember, but I agree, it's not perfect.
Hm, "values" would be nice, it's reserved in SQL:2016 [1] and in DB2/Mimer/MySQL/Oracle/SQL Server/Teradata [2], but unfortunately not in PostgreSQL [1], so perhaps not doable.
Syntax:
values.[schema name].[variable name]
[1] https://www.postgresql.org/docs/current/sql-keywords-appendix.html
[2] https://en.wikipedia.org/wiki/SQL_reserved_words
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2022-01-13 17:18:39 | Re: Avoiding smgrimmedsync() during nbtree index builds |
| Previous Message | Tom Lane | 2022-01-13 17:00:27 | Re: Time to drop plpython2? |