Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6])
	by hub.org (8.9.2/8.9.1) with ESMTP id JAA10575
	for <pgsql-interfaces@postgreSQL.org>;
	Mon, 1 Mar 1999 09:41:37 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id JAA14014;
	Mon, 1 Mar 1999 09:40:49 -0500 (EST)
To: bgunter@alef.gcsu.edu (Ben Gunter)
cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Tables acting funny with pgaccess 
In-reply-to: Your message of 28 Feb 1999 19:25:46 -0500
	<36D9DE96.49ED337@alef.gcsu.edu>
Date: Mon, 01 Mar 1999 09:40:48 -0500
Message-ID: <14012.920299248@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

bgunter@alef.gcsu.edu (Ben Gunter) writes:
> I'm having a problem with pgaccess that's confounding me.
> If I create a table with psql, I have no problems using pgaccess for
> queries.  However, if I create a table using pgaccess, things go awry. 

>> PostgreSQL error message: ERROR: func_get_detail: No such attribute or function 'lastname'

> It's only if I ask for a specific
> field from a table created by pgaccess.

At a guess, pgaccess is generating the table with case of field names
preserved?  Ordinarily, table and field names are implicitly downcased,
but not if you put double quotes around 'em.

My bet is that pgaccess is quoting your field names during CREATE TABLE
but not doing so during SELECT ... a bad combination.

			regards, tom lane