Message-ID: <002b01be63f4$4e555da0$29d710a8@lambda.gcsu.edu>
From: "Ben Gunter" <bgunter@alef.gcsu.edu>
To: "Constantin Teodorescu" <teo@flex.ro>, <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] Tables acting funny with pgaccess
Date: Mon, 1 Mar 1999 10:00:54 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I have attached the pg_dump output, but you probably won't need it.

When I got your message this morning, I started looking into the problem a
little further.  I found two things that I should have noticed before:

1) The problem only occurs when I use capital letters in the field names
(e.g., "FirstName", "LastName").  Field names consisting of all lower case
letters don't cause a problem.

2) If I enclose the field name in quotes when running the query (e.g.,
SELECT t0."LastName" FROM "Present" t0;), then everything works just fine.

That _almost_ solves my problems.  It would be nice if I could use the
visual query designer to run queries on tables with field names containing
upper case letters.  (But then again, I could just make all my field names
lower case and all would be well.)

I think Tom Lane is right.  It seems like field names are being quoted when
the table is created, but not when a query is executed.

Thanks for looking into it.

-Ben

-----Original Message-----
From: Constantin Teodorescu <teo@flex.ro>
To: pgsql-interfaces@postgreSQL.org <pgsql-interfaces@postgreSQL.org>
Date: Monday, March 01, 1999 2:17 AM
Subject: Re: [INTERFACES] Tables acting funny with pgaccess


>Ben Gunter wrote:
>>
>> > declare mycursor cursor for select t0.lastname from "Present" t0
>
>Send me a small pg_dump of that table with a few records.
>I will try it here.
>
>--
>Constantin Teodorescu
>FLEX Consulting Braila, ROMANIA
>
>