Re: SELECT problem

From: Grant Johnson <grant(at)amadensor(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thomas Lockhart <lockhart(at)fourpalms(dot)org>, Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, Andrew Sullivan <andrew(at)libertyrms(dot)info>, pgsql-general(at)postgresql(dot)org
Subject: Re: SELECT problem
Date: 2002-06-24 01:43:25
Message-ID: 3D16793D.3020307@amadensor.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I have worked with SQL server. It is a little weird as far as case. If
the table name is really upper case, you must type it upper case (it is
case sensitive, and does not default to upper case) I have been using
it lately in some classes for PeopleSoft, which puts the table names
upper case as per the standard (even if the standard is stupid). We use
Oracle at work, and it defaults to upper case, which is standard, but
ugly. As far as I can tell, the ODBC driver is case insensitive, but
the other tools that access the DB directly are case sensitive, whether
quoted or not. To force case within the ODBC, quote using [] rather
than "". I wish PeopleSoft supported Postgres. It is so much easier to
use.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Grant Johnson 2002-06-24 01:44:35 Re: SQL server application porting headache
Previous Message Stephan Szabo 2002-06-23 23:45:09 Re: foreign Key problem