From: Scott Marlowe <smarlowe@qwest.net>
To: Lars Erik Thorsplass <thorsplass@gmail.com>
Cc: pgsql-general@postgresql.org
Subject: Re: Stored procedures and "pseudo" fields..
Date: Tue, 20 Jul 2004 09:45:06 -0600
Message-ID: <1090338306.709.25.camel@localhost.localdomain> (raw)
In-Reply-To: <7eeb33a040720034319e036c6@mail.gmail.com>
References: <7eeb33a040720034319e036c6@mail.gmail.com>
On Tue, 2004-07-20 at 04:43, Lars Erik Thorsplass wrote:
> I have recently ventured into the exciting world of stored procedures,
> but I have now become lost.
>
> Background:
>
> Am currently working on access control in a web application. My goal
> is to process access control on the SQL level. This way if a row is in
> the result set, you have access to it, if not, you dont.
>
>
> Problem:
>
> My stored procedure "acl_check()" takes two integers as parameters.
> Param1 is the object id to check acl on, Param 2 is the object id of
> the user currently using the system. The procedure returns a positive
> numer (1 or 3 ) if you have some kind of access to the object. As one
> might understand I want the returned value from the acl_check()
> procedure to be a part of the result set.
>
> Kinda like this:
>
> SELECT *, acl_check( objects.obid, <user_id> ) AS mode FROM objects
> WHERE mode > 0;
Here's the problem. In order to do the select, the query first needs to
run the where clause. I.e.:
select a as test from table where a > 50;
works, but
select a as test from table where test > 50;
fails. The reason is that when the where clause fires first, there IS
no test yet, as it hasn't been materialized. what you need to do is:
select custom_function(a,b) from table where custom_function(a,b) > 0;
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: smarlowe@qwest.net, thorsplass@gmail.com, pgsql-general@postgresql.org
Subject: Re: Stored procedures and "pseudo" fields..
In-Reply-To: <1090338306.709.25.camel@localhost.localdomain>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox