Re: [GENERAL] id and ID in CREATE TABLE - Mailing list pgsql-sql

From stefan@extum.com
Subject Re: [GENERAL] id and ID in CREATE TABLE
Date
Msg-id Pine.LNX.4.44.0207201246180.3615-100000@extum.com
Whole thread Raw
Responses Re: [GENERAL] id and ID in CREATE TABLE  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-sql
Thanks all for comments. In Oracle and DB2 as far as I know the upper case
column names are used when you have no columns quoted.. Indeed it is
recommended to use lower cases to
avoid mistakes and confusion during porting. Is that right ?

But anyway this is not so important, but why upper cases are bad ?
Why then Oracle , IBM is using them and why the SQL standard is not
changed ?

stefan





On Fri, 19 Jul 2002, Martijn van Oosterhout wrote:

> On Sat, Jul 20, 2002 at 10:39:52AM +0300, 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 ...
>
> [snip]
>
> > Why is like this ? Why not letting them upper case if they are not quoted
> > ?
>
> I think it's because many people think that uppercase column names suck. And
> I agree with them. If you follow the given advice (either always quote
> column names or never) then not only will your program work, it's will be
> completely portable.
>
> So, if you'd used your CREATE TABLE statememnt below, you wouldn't have had
> this problem.
>
> > > CREATE TABLE ttt (
> > >
> > >     ID int2,
> > >     name text );
>


pgsql-sql by date:

Previous
From: Josh Jore
Date:
Subject: Re: id and ID in CREATE TABLE
Next
From: Charitha
Date:
Subject: Regarding replication