Received: from candle.pha.pa.us (216-55-132-35.dsl.san-diego.abac.net [216.55.132.35]) by postgresql.org (Postfix) with ESMTP id 3DC84475C3E; Fri, 19 Jul 2002 11:36:47 -0400 (EDT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id g6JFaJ611620; Fri, 19 Jul 2002 11:36:19 -0400 (EDT) From: Bruce Momjian Message-Id: <200207191536.g6JFaJ611620@candle.pha.pa.us> Subject: Re: [SQL] id and ID in CREATE TABLE In-Reply-To: To: stefan@extum.com Date: Fri, 19 Jul 2002 11:36:19 -0400 (EDT) Cc: pgsql-sql@postgresql.org, pgsql-general@postgresql.org X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200207/1223 X-Sequence-Number: 27710 stefan@extum.com wrote: > > I forgot about "" Sorry. So if I would use names quoted then my questions > are obsolete. Except one: > > So actually the only strange part would be PostgreSQL is folding to lower > cases a column name ... > > >From docs: > > The folding of unquoted names to lower case in PostgreSQL is > incompatible with the SQL standard, which says that unquoted names should > be folded to upper case. Thus, foo should be equivalent to "FOO" not > "foo" according to the standard. If you want to write portable > applications you are advised to always quote a particular name or never > quote it. > > > Why is like this ? Why not letting them upper case if they are not quoted > ? Well, historically, we always did lower case, and all-upper case looks ugly. That's about it. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026