| From: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
|---|---|
| To: | "Robin Helgelin" <lobbin(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: history table |
| Date: | 2007-08-21 19:42:58 |
| Message-ID: | 200708211342.58385.pgsql@bluepolka.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tuesday 21 August 2007 1:22 pm, Robin Helgelin wrote:
>
> Yes, this is where I'm too new to postgresql, how do I tell
> the database which user is logged in to the webapp? A session
> parameter? There will be connection pooling, but if I know how
> to solve the previous question I don't think it's hard to get
> it working with the pool.
Tablelog looks pretty cool. One way to handle your user ID issue
would be to initiate a user session by storing a session record
(for example: id, username, starttime), then have your app pass
that session ID to your updates for history. Then you could
store the user ID in an update_session_id column and tablelog
would help track of the history.
Ed
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Koterov | 2007-08-21 19:43:26 | Re: Need help doing a PostgreSQL vs Firebird feature comparison |
| Previous Message | Pavel Stehule | 2007-08-21 19:36:00 | Re: Array with Subselect / ANY - cast? |