Joe Conway wrote:
Andre wrote:
Package variables are not transactional, additionaly they are
session based - each session has it's own variables(values).
You can assign initial(defult) values in package spec.
Using table for them would also imply several columns
for each datatype or several tables
Andre wrote:
Package variables are not transactional, additionaly they are
session based - each session has it's own variables(values).
You can assign initial(defult) values in package spec.
Using table for them would also imply several columns
for each datatype or several tables for them.
I did a
Tom Lane wrote:
[EMAIL PROTECTED] writes:
Oracle has package level variables which are not mappable to any postgres
equivalent.
could we have something like schema scope variables which could be
directly referred from let's say plpgsql functions?
Can someone give me some pointers on how to go abo
[EMAIL PROTECTED] writes:
> Oracle has package level variables which are not mappable to any postgres
> equivalent.
> could we have something like schema scope variables which could be
> directly referred from let's say plpgsql functions?
> Can someone give me some pointers on how to go about imp
sorry my last mail went incomplete
please read through this and ignore my last mail
paraM
- Forwarded by Paramveer Singh/Trilogy on 20/09/2004 05:21 PM -
Paramveer Singh
20/09/2004 05:56 PM
To: [EMAIL PROTECTED]
cc:
Subject: sch
hi!
I apologize for mailing on the hackers list but I posted on the general list and did not get a good answer.
I have two independent issues, but am addressing them together.
1.
Oracle has package level variables which are not mappable to any postgres equivalent.
could we have something like sch
