Re: pl/sql cartridge and global varibales

The obvious answer is to put them into tables. If they are used frequently there should be virtually no disk i/o overhead.

If you want a completely off-the-wall idea though, you could write a PL/SQL package that sets the global variables you want, then goes into a loop waiting on a pipe with a published name.

Any other process that wants to handle a global variable could then send messages down the public pipe (passing a private pipe name for the reply).

--

Jonathan Lewis
Yet another Oracle-related web site: www.jlcomp.demon.co.uk

AleX wrote in message <377A4BE9.22937020_at_netwiz.net>...
>OK, this is really a follow-up to my previous posting...
>
>So I read that pl/sql catridges behaves as expected and treats all
>requests as individual
>sessions. This means that if I use one package to run multiple
>procedures, I cannot really
>user global variables in them, since the package will be
>discarded/re-created for each request.
>
>Is there a smart way to pass global values between the requests in this
>case?
>Any suggestions are super-welcome!
>
>
>Thanx,
>
> Alex.
>
Received on Wed Jun 30 1999 - 13:12:05 CDT