From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | Jake Stride <nsuk(at)users(dot)sourceforge(dot)net> |
Cc: | Bruno Wolff III <bruno(at)wolff(dot)to>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Constaints |
Date: | 2004-12-05 17:58:52 |
Message-ID: | 41B34C5C.5080504@Yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 12/5/2004 12:48 PM, Jake Stride wrote:
> Bruno Wolff III wrote:
>
>>On Sun, Dec 05, 2004 at 16:55:33 +0000,
>> Jake Stride <nsuk(at)users(dot)sourceforge(dot)net> wrote:
>>
>>
>>>Is there anyway to declare a constant that you can then use within a
>>>postgresql 'session', i am connecting from a PHP based application and
>>>trying to integrate another.
>>>
>>>
>>
>>At the worst you should be able to use a table with a row for each session
>>that includes the value to be used for each session.
>>
>>
> Would this be a postgresql session? If so how do I go about accessing it
> from a query/setting the value of it? I have looked at set authorization
> but I don't think this is where I should be looking!
PostgreSQL does not have userland session variables. You would have to
write some custom set/get functions in a procedural language that is
capable of holding global data across function calls (like PL/Tcl).
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Seltenreich | 2004-12-05 17:59:41 | Re: SSL confirmation |
Previous Message | Jake Stride | 2004-12-05 17:48:32 | Re: Constaints |