Ronnie Meier Ramos wrote:
Unfortunatly, faking them with some C functions would be very complex
because in this application's case most of this variables are record
types and some are arrays (pl/tables)... :-(
For record types, why not just use cursors? They can be made to persist
until the end
Thanks for all answers!
Unfortunatly, faking them with some C functions would be very complex
because in this application's case most of this variables are record
types and some are arrays (pl/tables)... :-(
It seems that creating temp tables (and some api functions) would be a
little bit easie
Ronnie Meier Ramos wrote:
AFAIK PG doesn't have packages - this is not a problem since I can
handle it with different schemas or some naming convention, but is there
a way to declare persistent variables (that would be "visible" to any
function up to the end of the session) ?
You might be able t
general@postgresql.org
[EMAIL PROTECTED] Subject: Re: [GENERAL]
Global/persistent variables
> AFAIK PG doesn't have packages - this is not a problem since I can
> handle it with different schemas or some naming convention, but is there
> a way to declare persistent variables (that would be "visible" to any
> function up to the end of the session) ?
AFAIK you'd have to fake it using a tem
Ronnie Meier Ramos <[EMAIL PROTECTED]> writes:
> AFAIK PG doesn't have packages - this is not a problem since I can
> handle it with different schemas or some naming convention, but is there
> a way to declare persistent variables (that would be "visible" to any
> function up to the end of the s
I'm analysing a conversion of a system from Oracle to PG. The system in
case uses a lot of PL/SQL packages and lots of them uses public/static
global/persistent variables declared inside its package specification or
body.
AFAIK PG doesn't have packages - this is not a problem since I can
handl
