From: | pgsql(dot)waldvogel(at)mac(dot)com |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Connection specific information - Temporary table used in Sybase to store information |
Date: | 2006-01-10 13:36:09 |
Message-ID: | 1610427.1136900169065.JavaMail.pgsql.waldvogel@mac.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello everybody,
Since I am new to PostgreSQL mailing lists, I am not sure which mailing list to use for my problem, I issue it to this group. If there is a more appropriate list, please let me know and I will happily post there.
The situation:
While porting an existing application from Sybase ASA to PostgreSQL 7.4 I need to access connection specific login data (user data). In the Sybase solution I used a temporary table (CREATE TEMPORARY TABLE). Each connection than had the table on connect; each client could then perform the INSERT statement without creating table. PostgreSQL differs from the behaviour as documented.
A lot of (very) different clients rely upon this this standard behaviour.
The question:
Is there any feature/technique that
a) can create temporary tables as in the SQL Standard defined
b) something like "ON CONNECT DO BEGIN .... END"? So that the temporary table can be automatically created upon connect?
Thanks in advance,
Kind regards,
Ralf
From | Date | Subject | |
---|---|---|---|
Next Message | John McCawley | 2006-01-10 14:06:51 | Re: Best programming language / connectivity for best performance |
Previous Message | surabhi.ahuja | 2006-01-10 13:10:58 | regarding triggers |