In-Reply-To: <20050419094846.21474.qmail@web50506.mail.yahoo.com>
References: <20050419094846.21474.qmail@web50506.mail.yahoo.com>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <3e03ba89a90fd8db93e69a441815e2db@mail.nih.gov>
Content-Transfer-Encoding: quoted-printable
Cc: pgsql-sql@postgresql.org
From: Sean Davis <sdavis2@mail.nih.gov>
Subject: Re: Query about SQL in PostgreSQL
Date: Tue, 19 Apr 2005 06:16:01 -0400
To: Muhammad Nadeem Ashraf <nadeem_engg@yahoo.com>


On Apr 19, 2005, at 5:48 AM, Muhammad Nadeem Ashraf wrote:

> Hi,
> I am new user of PostGreSQL 8.0.1. While using it i faced following=20
> issue. As SQL is Case insensetive Language So the Uper or Lower cases=20=

> are not significant. But while using the database there is problem.
> If i Create new Table with name (tblstudent) then upon SQL queries it=20=

> is fine to=A0use Select * from tblstudent. However i face probel if i=20=

> give the name of table in Capital letters i.e. if the name is=20
> (tblStudent) then upon using=A0Select * from tblStudent,=A0following =
error=20
> is appeard:
> ERROR:=A0 relation "tblst" does not exist=A0
> =A0
> And if i use the query Select * from "tblStudent" then it works fine.

SQL is case insensitive.  However, identifiers (table names, column=20
names, index names, etc.) are case sensitive in Postgresql.  So, your=20
operational understanding of how things work seems to be correct.  I=20
tend to use all lower-case, just because it saves me some thought, but=20=

I know some folks like to use a mix of upper and lower case so that=20
they can be used in a web application, for example.  If you do use=20
mixed or upper case, you do have to quote them.

If you still have a problem, could you be more specific about what it=20
is?

Sean