| From: | Eric E <whalesuit(at)bonbon(dot)net> |
|---|---|
| To: | pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: ODBC Rewrite |
| Date: | 2004-12-07 18:41:14 |
| Message-ID: | 41B5F94A.8090605@bonbon.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
While you all are doing this thinking, can I put in am idea?
I, like many others, am working on doing auditing in Postgres.
Something that would be very useful for auditing in a web application
environment would be to be able to pass various identifiers to the db
before any SQL statement is executed. In particular, I'm thinking of
something like Oracle's
SET_IDENTIFIER('string') feature (e.g.:
http://www.quest-pipelines.com/newsletter-v5/0604_C.htm) only
implemented through a driver hook, so that you could set the driver to
always pass this kind of identifier before executing any SQL. This
would allow a very straightforward way to manage users and auditing in a
setting where creating db users is not feasible, and it would be immune
to the problems of connection pooling.
Thoughts? Is this a bad thing to build into the driver?
Cheers,
Eric
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shachar Shemesh | 2004-12-07 21:24:32 | Re: ODBC Rewrite |
| Previous Message | markw | 2004-12-07 15:56:30 | Re: ODBC Rewrite |