From: Frank Bax <fbax@sympatico.ca>
To: me@shanewright.co.uk
Cc: pgsql-php@postgresql.org
Subject: Re: constants
Date: Mon, 04 Feb 2002 22:23:45 -0500
Message-ID: <3.0.6.32.20020204222345.02bd46e0@pop6.sympatico.ca> (raw)
In-Reply-To: <200202042134.g14LYFh23008@fullerruss.dsvr.co.uk>
References: <3.0.6.32.20020204161211.02c1b8d0@pop6.sympatico.ca>
<3.0.6.32.20020204161211.02c1b8d0@pop6.sympatico.ca>
I'm not sure; but I vaguely remember reading in pgsql-general that the
optimizer can tell if the function returns a constant, so only evaluate it
once. Yup, there it is:
http://archives.postgresql.org/pgsql-general/2001-03/msg01476.php
If you stick with one function per constant, it should still be fast. You
loose that if you go the table route, though; or even a case-type statement
within function.
Further details (and confirmation of statement about speed of 'constant'
functions) might be obtained by posting to pgsql-general.
Frank
At 09:33 PM 2/4/02 +0000, Shane Wright wrote:
>Hi Frank,
>
>Thanks, interesting idea - it looks like it would work fine, but wouldn't it
>be a little on the slow side?
>
>I like the constant table idea (hmm, could automatically populate the
>constant table by parsing my PHP definitions files, tasty...) - but again
>speed is of the essence...
>
>--
>Shane
>
>On Monday 04 Feb 2002 9:12 pm, Frank Bax wrote:
>> Try a pg function.
>>
>> http://www.postgresql.org/idocs/index.php?sql-createfunction.html
>>
>> CREATE FUNCTION one() RETURNS int4
>> AS 'SELECT 1 AS RESULT'
>> LANGUAGE 'sql';
>> SELECT one() AS answer;
>> answer
>> --------
>> 1
>>
>> If you are truly adventurous, you could create a 'constant' table and have
>> the function take an argument, which is key to the table.
>>
>> Frank
>>
>> At 02:00 PM 2/4/02 +0000, Shane Wright wrote:
>> >Hi
>> >
>> >This may be the wrong list to ask this, apologies if so :)
>> >
>> >Anyway, is there any way to define constants in PostgreSQL - my app has
>> > lots of them at the PHP level, but it'd be nice to use them directly in
>> > the SQL without overly complex query building.
>> >
>> >Something like this...
>> >
>> >DEFINE CONSTANT MYCONST = 4;
>> >
>> >SELECT * FROM mytable WHERE myfield=MYCONST;
>> >
>> >
>> >Thanks
>> >
>> >--
>> >Shane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-php@postgresql.org
Cc: fbax@sympatico.ca, me@shanewright.co.uk
Subject: Re: constants
In-Reply-To: <3.0.6.32.20020204222345.02bd46e0@pop6.sympatico.ca>
References: <3.0.6.32.20020204161211.02c1b8d0@pop6.sympatico.ca> <3.0.6.32.20020204222345.02bd46e0@pop6.sympatico.ca>
* 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