thanks.
Tom Lane wrote:
> [EMAIL PROTECTED] writes:
> > My troubles would be solved if I could reference a SessionID from
> > within PG. Any hope?
>
> Create a sequence. At session start, nextval() it to assign a session
> ID for your session. Then currval() returns your session ID whenever
>
[EMAIL PROTECTED] writes:
> My troubles would be solved if I could reference a SessionID from
> within PG. Any hope?
Create a sequence. At session start, nextval() it to assign a session
ID for your session. Then currval() returns your session ID whenever
you need it.
Hello All-
I am in the process of replacing the backend for a large MS Access
project with PG.
I really could use a Session ID. I would like to create a view like
this:
CREATE VIEW mysettings
AS
SELECT * FROM mysettingstable
WHERE sessionidcolumn = CURRENTSESSIONID()
It is ess
OK... so I see now that Access seems to be having a field day with
opening and closing sessions, in a way that seems out of my control.
This explains why my temporary table solutions (and then my plperl
global variable solution) were not working.
I will have to go with plan B.
I'd still
