From: | Alvaro Herrera <alvherre(at)atentus(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Masse Jacques <jacques(dot)masse(at)bordeaux(dot)cemagref(dot)fr>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pl/pgsql create table |
Date: | 2002-08-27 20:57:12 |
Message-ID: | Pine.LNX.4.44.0208271652450.5950-100000@cm-lcon1-46-187.cm.vtr.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Bruce Momjian dijo:
>
> When referencing created/dropped tables in pl/pgsql, use EXECUTE to
> prevent the table oid from being stored in function as precompiled. It
> is mentioned in the current FAQ. The solution is for us to
> automatically add EXECUTE somehow.
I don't understand. I think he is referring to the fact that the
function aborts midway because the DROP TABLE fails and marks the
transaction as failed. (but I didn't test before posting)
If that's the case, the solution would be to test for existance of the
table before the DROP TABLE statement.
> ---------------------------------------------------------------------------
>
> Masse Jacques wrote:
> > I have an error when tmp don't exist ( "table tmp don't exist" ...)
> >
> > and all is working well when there is a table tmp (no matter the structure
> > of this table, the new table has a structure according to foo)
--
Alvaro Herrera (<alvherre[a]atentus.com>)
"La gente vulgar solo piensa en pasar el tiempo;
el que tiene talento, en aprovecharlo"
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-08-27 21:01:19 | Re: pl/pgsql create table |
Previous Message | David Link | 2002-08-27 19:36:42 | Screwy behavior with SUM and multiple joins to same table |