Hello
no, it's not possible
Regards
Pavel Stehule
2011/5/2 Charles N. Charotti :
> Hello everybody !
>
> I want to know if I could share PLpgSQL variables between different
> functions and within different calls just using memory (not tables or other
> methods).
>
> If it is really possible ?
>
Hello everybody !
I want to know if I could share PLpgSQL variables between different functions
and within different calls just using memory (not tables or other methods).
If it is really possible ?
Thanks in advance,
Chuck
Steven Dahlin writes:
> In trying to call a postgresql 8.4 stored function I am passing a
> class as well as a List (I have to save a master record as well as the
> detail records). This is being done with a native query using
> EclipseLink 2.1. However, I am getting back a message for the first
>
manuel antonio ochoa writes:
> How can I solve this problem :
> FATAL: invalid cache id: 19
There was a bug with that symptom in 9.0.0 and 9.0.1 ... if you're
running one of those versions, update.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postg
Good morning !!
How can I solve this problem :
FATAL: invalid cache id: 19
2011-05-01 21:28:32 CDT feria uploader11 FATAL: the database system is
starting up
2011-05-01 21:28:32 CDT feria uploader11 FATAL: the database system is
starting up
2011-05-01 21:28:32 CDT feria uploader11 FATAL: th
In trying to call a postgresql 8.4 stored function I am passing a
class as well as a List (I have to save a master record as well as the
detail records). This is being done with a native query using
EclipseLink 2.1. However, I am getting back a message for the first
item:
PSQLException: Can't infe
I know that BIT and BIT VARYING types were deleted from SQL:2003 and
there are "old new" BINARY, BINARY VARYING in SQL:2008. I have two
question:
1) Are these types technically the same (I mean implementation things) ?
2) Is PostgreSQL aim to support BINARY, BINARY VARYING in 9.1 and
leave BIT and
