Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: Creating dynamically-typed tables using psycopg2's built-in
 formatting
From: Christophe Pettus <xof@thebuild.com>
In-Reply-To: 
 <VI1PR07MB579286D324415930A6E3E3A187EF0@VI1PR07MB5792.eurprd07.prod.outlook.com>
Date: Thu, 13 Jun 2019 13:35:15 -0700
Cc: "psycopg@postgresql.org" <psycopg@postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <628DF67F-7CFE-48DD-B01D-D7D7C9B53894@thebuild.com>
References: 
 <CAHAzoYkzXi1HFE0PmY3z0qn4SRnSZLdhChPUePf-2VwTM91upg@mail.gmail.com>
 <VI1PR07MB579286D324415930A6E3E3A187EF0@VI1PR07MB5792.eurprd07.prod.outlook.com>
To: David Raymond <David.Raymond@tomtom.com>
Precedence: bulk


> On Jun 13, 2019, at 13:29, David Raymond <David.Raymond@tomtom.com> =
wrote:
> For the capitalization thing basically what's going on is two things. =
(The way I understand it)
> 1) Postgres IS case sensitive.
> 2) When any query gets sent to the server, the server converts =
everything not inside quotes to lower case as step 1, _before_ trying to =
match names for tables, columns, functions, etc.

It's a bit more elaborate than that, although that's not a bad summary =
of the perceived result.  The details are here:

	=
https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-SYNTAX=
-IDENTIFIERS\

--
-- Christophe Pettus
   xof@thebuild.com