| From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Can we go beyond the standard to make Postgres radically better? |
| Date: | 2022-02-11 08:15:58 |
| Message-ID: | 59dbd63b-c9fb-3e72-cb58-a83f0e1e21cb@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2/10/22 10:33 PM, Raymond Brinzer wrote:
[snip]
> Here's one that I think is simple: why would we want a language where the
> clauses must come in a particular order? `FROM mytable SELECT column` is
> as clear an expression as `SELECT column FROM mytable`, and probably
> better, in that it starts with the source and winnows from there.
> Likewise, the order of WHERE, ORDER BY, and so on don't change what is
> being said.
>
> I believe the "why" is, "because parsing SQL is hard enough already", but
> that's a problem unto itself. A language with a more regular syntax is
> easier to work with and improve.
The answer is obvious to every grey beard: SQL was developed from SEQUEL,
Structured *ENGLISH* Query Language at a company that loved English-style
programming languages.
"SELECT column FROM mytable WHERE condition" is a perfect declarative
English sentence that any middle school grammar teacher would be proud of.
"FROM mytable SELECT column"... not so much.
--
Angular momentum makes the world go 'round.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Verite | 2022-02-11 13:35:33 | Re: Can we go beyond the standard to make Postgres radically better? |
| Previous Message | Guyren Howe | 2022-02-11 06:43:25 | Re: Can we go beyond the standard to make Postgres radically better? |