pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: sqllist <pgsql-sql@postgresql.org>
Cc: Jan Wieck <JanWieck@Yahoo.com>
Subject: Re: Huh? Mysterious Function Error
Date: Tue, 20 Feb 2001 12:36:52 -0500
Message-ID: <15771.982690612@sss.pgh.pa.us> (raw)
In-Reply-To: <3A92A15E.1E7DF00D@agliodbs.com>
References: <3A92A15E.1E7DF00D@agliodbs.com>

Josh Berkus <josh@agliodbs.com> writes:
> ERROR:  unexpected SELECT query in exec_stmt_execsql()

plpgsql doesn't think you should execute bare SELECTs, only SELECT INTO.

On reflection this seems an overly anal-retentive restriction, since
there are cases where one might execute a SELECT for its side effects
alone ("SELECT setval()" comes to mind).

Jan, do you think there's a good case for refusing plain SELECTs?

			regards, tom lane



view thread (4+ messages)  latest in thread

Message-ID: <15771.982690612@sss.pgh.pa.us>
Permalink:  ../15771.982690612@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/15771.982690612@sss.pgh.pa.us

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com, JanWieck@Yahoo.com
  Subject: Re: Huh? Mysterious Function Error
  In-Reply-To: <15771.982690612@sss.pgh.pa.us>
  References: <3A92A15E.1E7DF00D@agliodbs.com> <15771.982690612@sss.pgh.pa.us>

* 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