Skip site navigation (1) Skip section navigation (2)

Re: Probably a stupid question

From: "Chad Thompson" <chad(at)weblinkservices(dot)com>
To: "Giorgio Ponza" <g(dot)ponza(at)opla(dot)it>, <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Probably a stupid question
Date: 2003-06-27 20:16:17
Message-ID: 011701c33ce8$f801e9a0$32021aac@chad (view raw, whole thread or download thread mbox)
Lists: pgsql-novice
I believe your problem is simply with the case of the table name.  You might
want to try \d mirrorhosts.  If the table was created "MirrorHosts" (which
it looks like it was) postgresql will store that name and you will be
required to reference it like that.

I believe there is something in the docs about case sensitivity, but I cant
seem to find it now.

----- Original Message ----- 
From: "Giorgio Ponza" <g(dot)ponza(at)opla(dot)it>
To: <pgsql-novice(at)postgresql(dot)org>
Sent: Friday, June 27, 2003 1:37 AM
Subject: [NOVICE] Probably a stupid question

> Hi all, and tx for all the help you give to the community
> I have a question, really stupid, but i'd like to understand the postgres
> behavior.
> I installed dbmirror, and there is a file script creating a table,
> like this:
> CREATE TABLE "MirrorHosts" ..... etc etc
> Ok, no prob with the syntax (3 years i use postgreSQL), but when i use
> i have this problems:
> 1) the command \d MirrorHosts doesn't work (table MirrorHost not found),
>    i have to use \d "MirrorHosts"
> 2) when i do SELECT * FROM MirrorHosts;   (the same prob)
>    i have to use "MirrorHosts"
> I'd like to know if there is a way to bypass this problem.
> Tx in advance and ..... PostgreSQL is really GREAT!
> Giorgio Ponza
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>       joining column's datatypes do not match

In response to

pgsql-novice by date

Next:From: Nabil SayeghDate: 2003-06-27 20:21:17
Subject: Re: connectby_reverselookup()
Previous:From: Nabil SayeghDate: 2003-06-27 19:35:14
Subject: ERROR: tuplestore_gettuple: invalid state

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group