Message-ID: <419B6D27.5020804@archonet.com>
Date: Wed, 17 Nov 2004 15:24:23 +0000
From: Richard Huxton <dev@archonet.com>
User-Agent: Mozilla Thunderbird 0.9 (X11/20041103)
MIME-Version: 1.0
To: abief_ag_-postgresql@yahoo.com
Cc: pgsql-sql@postgresql.org
Subject: Re: session_id
References: <20041117142525.97895.qmail@web13924.mail.yahoo.com>
In-Reply-To: <20041117142525.97895.qmail@web13924.mail.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Riccardo G. Facchini wrote:
>>Add a new sequence to your database:
>>   CREATE SEQUENCE my_session_id;
>>
>>Then, at the start of every session:
>>   SELECT nextval('my_session_id');
>>
>>and whenever you need the value:
>>   SELECT currval('my_session_id');

> Good idea, but it won't work for what I need.
> I'll be able to do get the nextval('my_session_id') as soon as the
> session initiates, but my problem is that I need to make all the
> subsecuent actions aware of that particular value. using
> currval('my_session_id') is not good, as any other session is likely to
> also change my_session_id to another value.

No - other sessions will see different values. Test it and see.
-- 
   Richard Huxton
   Archonet Ltd