From: | Darren Duncan <darren(at)darrenduncan(dot)net> |
---|---|
To: | "pgadmin-support(at)lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org> |
Subject: | Re: purple letters |
Date: | 2017-09-25 20:53:10 |
Message-ID: | f879c107-b60a-23ae-ba99-f95c738c02a0@darrenduncan.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
For my part, when I designed my programming language, I intentionally did not
use single-letter names for any keywords or reserved words or system-defined
entities etc, and all built-ins were either 2+ letters or were symbols. As a
result, single-letter names are available/reserved for end users as barewords to
name their own (presumably narrow-lexical-scope) stuff, without having to guess
which letters they may use. -- Darren Duncan
On 2017-09-22 8:05 AM, Murtuza Zabuawala wrote:
> The characters which are in purple colour are are valid SQL keywords hence
> highlighted by CodeMirror :-)
> Ref: https://www.postgresql.org/docs/10/static/sql-keywords-appendix.html
>
> On Fri, Sep 22, 2017 at 1:53 PM, Hibbard, Brandon
> wrote:
>
> I have a quick question on the code highlighting. I often use a single
> character as an alias for tables in joins. I have noticed that some
> letters are colored purple while others are black. Is there a reason
> for this? I have attached an image showing what I mean. The image was
> taken from version 2.0-rc2.
From | Date | Subject | |
---|---|---|---|
Next Message | Siddharth Divi | 2017-09-26 01:26:09 | Inability to export data as '.csv' file in pgAdmin4 |
Previous Message | Hibbard, Brandon | 2017-09-25 17:07:52 | RE: purple letters |