A big thanks to Brian Hurt, Michael Fuhr and Michael Glaesemann for
pointing out the need to quote case-sensitive table and column
names. Because I tend to search the documentation when I run into a
problem, rather than go through the docs thoroughly (all good
programmers *always* read the docs fully first , right? LOL), I was
not aware of the quote need.
Thanks again for the help. I am transitioning from MS-Access to C#
and Npgsql. What a challenge, to say the least! Someone could make
a ton of money writing an Access-to-C# converter program... LOL!
On Jul 30, 2007, at 9:26 AM, Dale Seaburg wrote:
> I have a database that can be accessed and used correctly via ODBC
> and MS-Access. But when I try to do a simple SQL SELECT query in
> psql, I get an error that the table can't be found: Relation
> "instrument_type" does not exist. Yet, when I do a "\d" command, I
> see the table named "Instrument_Type" in the "public" schema. I
> use the database owner as the user id for psql.
> I need some help where to look in, say pgAdmin III (my tool of
> choice for database creation / maintenance) for a clue as to why I
> am getting this error.
> Thanks for any help, ideas, clues, starting points.
> ---------------------------(end of
> TIP 4: Have you searched our list archives?
In response to
pgsql-novice by date
|Next:||From: Christian Leclerc||Date: 2007-07-30 16:40:19|
|Subject: Auto-vacuum parameters (Postgres 8.2 on Windows Server 2003)|
|Previous:||From: Michael Glaesemann||Date: 2007-07-30 14:51:57|
|Subject: Re: Not able to find a table|