From: Kristis Makris <kristis.makris@datasoft.com>
To: Richard Huxton <dev@archonet.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Using the extract() function in plpgsql
Date: 26 Jun 2001 12:58:51 -0700
Message-ID: <200106261958.f5QJwsa45412@postgresql.org> (raw)
In-Reply-To: <003701c0fa5e$722570a0$1001a8c0@archonet.com>
References: <200106202233.f5KMXSa91452@postgresql.org>
<003701c0fa5e$722570a0$1001a8c0@archonet.com>
On 21 Jun 2001 15:28:29 +0100, Richard Huxton wrote:
> From: "Kristis Makris" <kristis.makris@datasoft.com>
>
> > Hi Peter,
> >
> > Thanks for looking into this. I tried the CREATE TABLE AS syntax within
> > an EXECUTE command but I still get the same error message. The CREATE
> > TABLE AS docs mention that this syntax is "functionalily equivalent" to
> > the SELECT INTO, so it's no surprise that I get the same error message:
> >
> > NOTICE: The execStmt is: CREATE TEMPORARY TABLE test AS SELECT
> > extract(epoch from interval '62 days 22:30:48')
> > ERROR: EXECUTE of SELECT ... INTO is not implemented yet
>
> In the example above you can just CREATE the table then INSERT into it -
> avoids the whole issue. Is the example accurate?
>
> - Richard Huxton
Creating the temporary table first, and then inserting into it seems to
be a *somehow* functional workaround. However, the function cannot be
called again a second time during the same session, since the temporary
table already exists. Is there a way a table can be created truly
temporary, existing only within the scope of a plpgsql function?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: kristis.makris@datasoft.com, dev@archonet.com
Subject: Re: Using the extract() function in plpgsql
In-Reply-To: <200106261958.f5QJwsa45412@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox