From: Scott Marlowe <scott.marlowe@gmail.com>
To: Csaba Együd <csegyud@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Separate Sessions?? (View data <-> Query tool)
Date: Tue, 25 Nov 2008 10:12:55 -0700
Message-ID: <dcc563d10811250912h40956d32y6ba35fbf9ff75527@mail.gmail.com> (raw)
In-Reply-To: <ggh0on$2167$1@news.hub.org>
References: <ggh0on$2167$1@news.hub.org>
2008/11/25 Csaba Együd <csegyud@gmail.com>:
> Hi,
> I'm administering a Pg8.3 database with PgAdmin3.
>
> The users need views "pre" filtered on a session based vairable wich is
> stored in a temporary table. Immediately after logging into the database the
> client software creates a temporary table and stores an idin that. The users
> query views when they want to see the contents of a filtered table and
> modify the tables directly - which tables have BEFORE UPDATE/DELETE/INSERT
> trigers to check the existence of the Temp table and to force filter field
> values to be defaulted to the temporary table field. I hope it is clear...
> :)
>
> When I log in with PgAdmin I have to create the temp table manually. It's
> ok, and if I use the query tool i cansee query the views after creating the
> temp table. But if I want to see the contents of a view in table view (View
> Data-View all rows), the views are empty indicating that it lacks of the
> temporary table. When I view directly the table (not the view) and try to
> edit a field the trigger refuses it because of the lack of temp table.
I'm guessing that you're creating tables like:
create temporary table blah blah blah
and can't see them from other connections? That's normal. If you
want to be able to see tables from multiple sessions you need to
create regular tables.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott.marlowe@gmail.com, csegyud@gmail.com
Subject: Re: Separate Sessions?? (View data <-> Query tool)
In-Reply-To: <dcc563d10811250912h40956d32y6ba35fbf9ff75527@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox