On Fri, 19 Jul 2002, Tom Lane wrote:
> "scott.marlowe" <[EMAIL PROTECTED]> writes:
> > Agreed. Absolutely. But, since the SQL standard says upper case,
> > wouldn't it be useful to at least have a switch (run time, initdb time,
> > or ./configure time???) called something like FOLDTOUPPER (in
On Fri, 19 Jul 2002, Bruce Momjian wrote:
> scott.marlowe wrote:
> > On Fri, 19 Jul 2002, Tom Lane wrote:
> >
> > > [EMAIL PROTECTED] writes:
> > > > But anyway this is not so important, but why upper cases are bad ?
> > >
> > > It's well established that all-lower-case text is more readable th
On Fri, 19 Jul 2002, Tom Lane wrote:
> [EMAIL PROTECTED] writes:
> > But anyway this is not so important, but why upper cases are bad ?
>
> It's well established that all-lower-case text is more readable than
> all-upper-case ...
Agreed. Absolutely. But, since the SQL standard says upper cas
On Sat, Jul 20, 2002 at 10:39:52AM +0300, [EMAIL PROTECTED] 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
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 cas
