Re: [SQL] distinguishing different database connections - Mailing list pgsql-interfaces

From Christof Glaser
Subject Re: [SQL] distinguishing different database connections
Date
Msg-id 01062210383901.00729@pinguin
Whole thread Raw
In response to distinguishing different database connections  (Markus Wagner <wagner@imsd.uni-mainz.de>)
List pgsql-interfaces
Hi Markus,

On Friday, 22. June 2001 09:59, Markus Wagner wrote:
> Hi,
>
> can I access information on the current connection from within a
> trigger function?
> I need to identify different server connections somehow. Something
> like a "connection id" would be enough.

I think, there is no such thing like a connection id.

> The background:
>
> When a user starts a frontend application (NT, Access) he starts a
> new connection to our Linux database server. But for all users the
> "postgres user" is the same, since the ODBC connection is hard linked
> into the application. The problem is that we need the NT user name
> within our trigger (C) functions.
>
> The idea:
> Let's execute a function "logon" whenever an instance of the
> application is started. This function will get the NT user name as a
> parameter. It will recognize the current connection id and it would
> store the pair (connection id, NT user name) in a table. Then,
> whenever some trigger needs to know the user name (for logging
> actions), it could lookup the user name with the current connection
> id.

What about looking how web applications handle this? A "session id", 
which you have to manage yourself, might do what you want:

<just_an_idea>
- logon creates a session id
- actions that need to keep track of users should be done within 
functions called by the client, providing the session id as a parameter.
</idea>

HTH.
Christof


pgsql-interfaces by date:

Previous
From: "Paul Grenda"
Date:
Subject: Re: jbuilder and postgres
Next
From: "Eduardo Kotujansky"
Date:
Subject: tutorial java + postgresql