Re: SELECT is causing a runtime error when used in stored functions: State=42601, Err=7, Msg=ERROR: query has no destination for result data; - Mailing list pgsql-general

From Raymond O'Donnell
Subject Re: SELECT is causing a runtime error when used in stored functions: State=42601, Err=7, Msg=ERROR: query has no destination for result data;
Date
Msg-id 4B520CAD.1030908@iol.ie
Whole thread Raw
In response to SELECT is causing a runtime error when used in stored functions: State=42601, Err=7, Msg=ERROR: query has no destination for result data;  ("Lothar Bongartz" <lbongartz@moove.com>)
List pgsql-general
On 16/01/2010 13:47, Lothar Bongartz wrote:
> State=42601, Err=7, Msg=ERROR: query has no destination for result data;
> Example:
>
> CREATE OR REPLACE FUNCTION MyTest
> (
>       IN OUT      v_1 int
> ) AS $$BEGIN
>       SELECT v_1 = 1;
> END;$$ LANGUAGE plpgsql

The error message says it all - in plpgsql you need to specify a
destination variable for the result of the SELECT.

  create....
  as
  $$
  declare
    m_result integer;
  begin
    select 1 into m_result;
    return m_result;
  end;
  $$
  language plpgsql;

If you use an OUT parameter as you did in your example, you don't need
the "return m_result;", though you might still need a "return;" to end
the function - not sure on this one.

Ray.


--
Raymond O'Donnell :: Galway :: Ireland
rod@iol.ie

pgsql-general by date:

Previous
From: "Lothar Bongartz"
Date:
Subject: SELECT is causing a runtime error when used in stored functions: State=42601, Err=7, Msg=ERROR: query has no destination for result data;
Next
From: Mathieu De Zutter
Date:
Subject: Re: Constraint exclusion issue