Andrew,
That is acutally what the second run was supposed to be. I copied the
original on instead of the second instance, but the results were the
same.
Michael Gould
Intermodal Software Solutions, LLC
904-226-0978
-------- Original Message --------
Subject: Re: [GENERAL] problem trying to create a temp table
From: Andrew Gould <andrewlylegould@gmail.com>
Date: Fri, February 24, 2012 6:41 am
To: mgould@isstrucksoftware.net
Cc: Richard Huxton <dev@archonet.com>, "pgsql-general@postgresql.org"
<pgsql-general@postgresql.org>
On Fri, Feb 24, 2012 at 7:36 AM, <mgould@isstrucksoftware.net> wrote:
How do I access it. I just did that and when I try and access it with a
ERROR: relation "sessionsetting" does not exist
LINE 1: select * from "sessionsetting"
^
********** Error **********
ERROR: relation "sessionsetting" does not exist
SQL state: 42P01
Character: 15
or
ERROR: relation "sessionsetting" does not exist
LINE 1: select * from "sessionsetting"
^
********** Error **********
ERROR: relation sessionsetting does not exist
SQL state: 42P01
Character: 15
Best Regards,
Michael Gould
Intermodal Software Solutions, LLC
904-226-0978
-------- Original Message --------
Subject: Re: [GENERAL] problem trying to create a temp table
From: Richard Huxton <dev@archonet.com>
Date: Fri, February 24, 2012 6:32 am
To: mgould@isstrucksoftware.net
Cc: "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
On 24/02/12 13:26, mgould@isstrucksoftware.net wrote:
> ALL,
> Using 9.1.2 on Windows 7 X64 for development.
> I'm trying to create a temporary table used to store session variables
> CREATE TEMP TABLE iss.sessionsettings
> When I try and run this I get the following error message.
> ERROR: cannot create temporary relation in non-temporary schema
Temp tables get their own schema, and each session (connection) gets
its own temp schema. So - don't qualify them by schema.
--
Richard Huxton
Archonet Ltd
Try to access the table without putting the table name in double quotes.
Does that make a difference?
Andrew
