From: David A. Leedom <daleedom@hightowergroup.com>
To: Anjan Dave <adave@vantage.com>
To: pgsql-admin@postgresql.org
Subject: Re: Temporary Tables
Date: Tue, 21 Jun 2005 10:43:10 -0400
Message-ID: <6.1.2.0.2.20050621102941.03118720@mail.hightowergroup.com> (raw)
In-Reply-To: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78502EA14CB@vt-pe2550-001.van tage.vantage.com>
References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78502EA14CB@vt-pe2550-001.vantage.vantage.com>
Anjan,
I would be very interested in this feature as well. However, my
understanding is that you must keep the connection open AND your
application must retain the SAME connection between database interactions.
The only way that I have done this is by creating a Session ID column to
your table of interest and make it a permanent table. The application then
maintains the Session ID in memory and uses it to segregate the data from
various users.
My main interest in this is to create my own user table which triggers on
other tables will somehow use to know that a specific user is making a
change on a specific row(s).
How do others handle this issue?
Enthusiastically,
Dave Leedom
At 11:20 AM 6/20/2005, Anjan Dave wrote:
>Hi,
>
>A developer is trying to use a Temporary Table via the java based
>application. The problem is following the temp table creation, he wants
>subsequent queries to query the temp table, but they are not in the same
>database session as the temp table. Is this something I can setup
>somewhere in the config? I would appreciate any pointers/info I can
>forward to him.
>
>Thanks,
>Anjan
>
>
>******************************************************************************************
>This e-mail and any files transmitted with it are intended for the use of the
>addressee(s) only and may be confidential and covered by the attorney/client
>and other privileges. If you received this e-mail in error, please notify
>the
>sender; do not disclose, copy, distribute, or take any action in reliance on
>the contents of this information; and delete it from your system. Any other
>use of this e-mail is prohibited.
>******************************************************************************************
>
The Hightower Group, Inc.
Custom Software Solutions Designed To Fit Your Business Like A Glove.
165 West Airport Road, Suite B/Lititz, PA 17543
V:717-560-4002, 877-560-4002 x: 114
F:717-560-2825
www.hightowergroup.com
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: daleedom@hightowergroup.com, adave@vantage.com
Subject: Re: Temporary Tables
In-Reply-To: <6.1.2.0.2.20050621102941.03118720@mail.hightowergroup.com>
References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78502EA14CB@vt-pe2550-001.vantage.vantage.com> <6.1.2.0.2.20050621102941.03118720@mail.hightowergroup.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