pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ben Gunter <bgunter@alef.gcsu.edu>
To: Constantin Teodorescu <teo@flex.ro>
To: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Tables acting funny with pgaccess
Date: Mon, 1 Mar 1999 10:02:09 -0500
Message-ID: <004201be63f4$7a9815b0$29d710a8@lambda.gcsu.edu> (raw)

Oops...here's the attachment.

-----Original Message-----
From: Ben Gunter <bgunter@alef.gcsu.edu>
To: Constantin Teodorescu <teo@flex.ro>; pgsql-interfaces@postgreSQL.org
<pgsql-interfaces@postgreSQL.org>
Date: Monday, March 01, 1999 10:00 AM
Subject: Re: [INTERFACES] Tables acting funny with pgaccess


>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
>>
>>
>

Attachments:

  Present.out (application/octet-stream, 439B) download

view thread (6+ messages)  latest in thread

Message-ID: <004201be63f4$7a9815b0$29d710a8@lambda.gcsu.edu>
Permalink:  ../004201be63f4$7a9815b0$29d710a8@lambda.gcsu.edu/
Also on:    postgresql.org/message-id/004201be63f4$7a9815b0$29d710a8@lambda.gcsu.edu

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: bgunter@alef.gcsu.edu, teo@flex.ro
  Subject: Re: [INTERFACES] Tables acting funny with pgaccess
  In-Reply-To: <004201be63f4$7a9815b0$29d710a8@lambda.gcsu.edu>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox