OK, I see. I first used the Postgres admin tool in webmin (Linux/unix
web admin tool)
to create the first table. I guess that it quoted my "Project" table.
Anyhow, I dropped
the table from the same tool, and then went to DBVisualizer and
recreated all my tables
there, using uppercase for all tab
On Mon, Feb 28, 2005 at 12:50:25PM +0100, Tommy Svensson wrote:
> - I've used Oracle, DB2, Mimer, and HSQLDB before, and my experience
> with these led me
> to beleive that SQL was case insensitive. In fact, I was so sure of it
> that a case problem
> just never occured to me.
Case isn't a pr
Tommy Svensson presumably uttered the following on 02/27/05 18:50:
I have just installed Postgresql and tried it for the first time.
One very serious problem I ran into was when actually trying to use
created tables.
Creating a simple table without any foreign keys works OK, but after
creating t
Try putting quotes around the table name:
select * from "Table";
?
Do you see it in the table list?
\dt
Tommy Svensson wrote:
I have just installed Postgresql and tried it for the first time.
One very serious problem I ran into was when actually trying to use
created tables.
Creating a simple tabl
On Sun, 2005-02-27 at 18:50 -0500, Tommy Svensson wrote:
> I have just installed Postgresql and tried it for the first time.
>
> One very serious problem I ran into was when actually trying to use
> created tables.
> Creating a simple table without any foreign keys works OK, but after
> creating
On Sun, 27 Feb 2005, Tommy Svensson wrote:
> I have just installed Postgresql and tried it for the first time.
>
> One very serious problem I ran into was when actually trying to use
> created tables.
> Creating a simple table without any foreign keys works OK, but after
> creating the
> table it
Am Sonntag, den 27.02.2005, 18:50 -0500 schrieb Tommy Svensson:
> I have just installed Postgresql and tried it for the first time.
>
> One very serious problem I ran into was when actually trying to use
> created tables.
> Creating a simple table without any foreign keys works OK, but after
> c
Thanks for all the replys, I got quite a lot of them, and haven't had
time to read them all yet, but
one common comment I get is "You didn't supply enough information" , "be
more specific", etc.
You are of course right.
From the answers I got however, it seems to be a very high propability
that
On Sun, Feb 27, 2005 at 06:50:50PM -0500, Tommy Svensson wrote:
> SELECT * FROM ;
> SELECT * FROM public.;
> SELECT * FROM .public.;
>
> All result in the message "The relation does not exist!" or "The
> relation public. does not exist!".
Could you copy and paste the *exact* commands and error
On Sun, 2005-02-27 at 18:50 -0500, Tommy Svensson wrote:
>I have just installed Postgresql and tried it for the first time.
>
>One very serious problem I ran into was when actually trying to use
>created tables.
>Creating a simple table without any foreign keys works OK, but after
>creating the
>
Tommy Svensson <[EMAIL PROTECTED]> writes:
> I have just installed Postgresql and tried it for the first time.
>
> One very serious problem I ran into was when actually trying to use
> created tables.
> Creating a simple table without any foreign keys works OK, but after
> creating the
> table it
I have just installed Postgresql and tried it for the first time.
One very serious problem I ran into was when actually trying to use
created tables.
Creating a simple table without any foreign keys works OK, but after
creating the
table it is not possible to do a select on it! I tried the follow
12 matches
Mail list logo
