Re: OidFunctionCall* returning null.

From: David Zwarg <dzwarg+postgis(at)azavea(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: OidFunctionCall* returning null.
Date: 2011-11-18 16:37:08
Message-ID: CANSnHN2myL+fOq5T=zovxNM3DOgy1WALXvZkjSD1fjS0r1=A0Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I just found this thread:

http://archives.postgresql.org/pgsql-general/2011-11/msg00424.php

So I'll use the same workaround.

Nothing to see here, folks, move along....

d

On Fri, Nov 18, 2011 at 11:17 AM, David Zwarg <dzwarg+postgis(at)azavea(dot)com>wrote:

> Hello,
>
> I have been working with the PostGIS developers, and I'm implementing a
> facility to use 'callback' functions to process cells in a raster image.
>
> I have implemented this behind the scenes as a C function that calls a
> provided sql regprocedure with OidFunctionCall*. I have been reading the
> docs, and it states that "Note that neither arguments nor result are
> allowed to be NULL."
>
> In this use case, there are legitimate reasons to return NULL from a
> 'callback' function -- is there an alternative method that I should use,
> instead of OidFunctionCall*?
>
> Thanks,
> David
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2011-11-18 16:56:06 Re: range_adjacent and discrete ranges
Previous Message Robert Haas 2011-11-18 16:33:04 Re: testing ProcArrayLock patches