Feedback-ID: ie0a040ee:Fastmail
Message-ID: <a94be92e-584f-45e3-a5d8-ba2f00cd7a44@eisentraut.org>
Date: Fri, 3 May 2024 13:27:58 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: The PostgreSQL Select Syntax
To: mohamedhussein10445@gmail.com, pgsql-docs@lists.postgresql.org
References: <171467330713.708.11362279483258372836@wrigleys.postgresql.org>
Content-Language: en-US
From: Peter Eisentraut <peter@eisentraut.org>
In-Reply-To: <171467330713.708.11362279483258372836@wrigleys.postgresql.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/a94be92e-584f-45e3-a5d8-ba2f00cd7a44%40eisentraut.org>
Precedence: bulk

On 02.05.24 20:08, PG Doc comments form wrote:
> I'm writing to seek clarification regarding the scope of the formal syntax
> outlined in the documentation for the SELECT statement
> (https://www.postgresql.org/account/comments/new/16/sql-select.html/).
> 
> I understand that this syntax defines the core structure and rules for
> constructing valid queries. However, I'm interested in building an
> Object-Relational Mapper (ORM) for PostgreSQL.
> 
> My primary question is: Does the documented formal syntax represent the
> absolute limit of what PostgreSQL can understand and process, or are there
> additional functionalities beyond these core rules?

The documentation on those reference pages like the one you show for 
SELECT is intended to be a complete description of the syntax and 
semantics of the command.

But there is additional relevant information in other parts of the 
documentation, such as the basic elements SQL syntax, or the input and 
output formats of data types.