Re: [GENERAL] Stored procedures and "pseudo" fields.. - Mailing list pgsql-sql

From Lars Erik Thorsplass
Subject Re: [GENERAL] Stored procedures and "pseudo" fields..
Date
Msg-id 7eeb33a040720150320bf5eed@mail.gmail.com
Whole thread Raw
List pgsql-sql
On Tue, 20 Jul 2004 09:45:06 -0600, Scott Marlowe <smarlowe@qwest.net> wrote:
> > 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;
> 
> 

Thanks for clearing that up. I just hoped there was some magic I could
sprinkle on my query to get away from the extra overhead of running
the procedure twice :)

Best regards..

L.E.Thorsplass


pgsql-sql by date:

Previous
From: Steve Crawford
Date:
Subject: Re: locks and triggers. give me an advice please
Next
From: azah azah
Date:
Subject: date_format in postresql