Re: Stored function RETURNS table, but in some cases columns are missing - should I set them to NULL?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alexander Farber <alexander(dot)farber(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Stored function RETURNS table, but in some cases columns are missing - should I set them to NULL?
Date: 2021-03-08 19:53:41
Message-ID: 1842232.1615233221@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alexander Farber <alexander(dot)farber(at)gmail(dot)com> writes:
> However there are cases, when I only have the out_gid value, I do not want
> to return any other values.
> My question is: do I have to set the other OUT params explicitly to NULL?

plpgsql initializes them to null by default, I believe, just like ordinary
local variables.

> org.postgresql.util.PSQLException: ERROR: column "out_uid" does not exist|

This isn't related to what your function does internally.

I think the issue is you renamed out_uid to uid in your SELECT:

> String SQL_JOIN_GAME =
> "SELECT " +
> "out_uid AS uid, " +

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Munro 2021-03-08 21:25:59 Re: Log files polluted with permission denied error messages after every 10 seconds
Previous Message Osvaldo Kussama 2021-03-08 19:41:55 Re: Question about when PostgreSQL 11.0 was released