From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | mpg4(at)duluoz(dot)net |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: [SQL] Getting environment variables? |
Date: | 2000-01-16 17:13:34 |
Message-ID: | Pine.LNX.4.21.0001151952060.386-100000@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On 2000-01-12, mpg4(at)duluoz(dot)net mentioned:
> I'd like to be able to create a view like this:
>
> create view my_view as select * from real_table where check_cred(row.id)
>
> where check_cred(row.id) is a function that checks for some externally
> available credential or 'ticket' and only shows the rows in the table
> that the id is allowed to see. Basically, I want to create 'virtual
> users' inside of my database without creating a separate view for each
> user. My problem is getting check_cred() to see the 'ticket' without
> having it passed in with the query.
I don't see this working out. Somehow you'd have to get the information on
the server host, there's no official way to abuse the PostgreSQL
connection for other purposes.
>
> Environment variables won't workas the backend executes the query,
> and doesn't have my environment. Some client/server thing would work,
> I suppose, but I don't really want to code one if it can be avoided.
> Is there an easier solution?
>
> Also, is there a repository for user-created postgresql
> types/functions anywhere? Some of the things I'm doing have to have
> been done already, and done better.
>
> Thanks,
>
> -mike
>
>
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2000-01-16 17:14:04 | Re: [SQL] numeric question.. |
Previous Message | Marc Tardif | 2000-01-16 13:20:03 | attribute level rules not supported? |