Re: Audit-trail engine: getting the application's layer user_id

From: Manuel Sugawara <masm(at)fciencias(dot)unam(dot)mx>
To: Tilmann Singer <tils-pgsql(at)tils(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Audit-trail engine: getting the application's layer user_id
Date: 2007-04-25 14:42:30
Message-ID: m3fy6oqzvt.fsf@conexa.fciencias.unam.mx
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tilmann Singer <tils-pgsql(at)tils(dot)net> writes:

> Can I define a view which references a table in a way so that it will
> use a temporary table of the same name if it exists, otherwise the
> permanent table with that name?

I think you can use a plpgsql function with execute. For instance, if
the name of your temp table is current_user_id the function will be
something like:

create function get_current_user_id() returns int as $$
declare
v_rec record;
v_user int;
v_query text;
begin
v_query := 'SELECT user_id FROM current_user_id';
for v_rec in execute v_query loop
v_user := v_rec.user_id;
end loop;
return v_user;
end;
$$ language plpgsql;

Untested but that's the idea, you need to use execute to avoid the
caching of the plan. You might also want to control what happens when
the table does not exist and that can be done handling the
corresponding exception. Check the docs for the details.

Regards,
Manuel.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Simon Riggs 2007-04-25 14:42:33 Re: [DOCS] Incrementally Updated Backups: Docs Clarification
Previous Message Richard Huxton 2007-04-25 14:35:01 Re: pg_connect sometimes works sometimes not