Skip site navigation (1) Skip section navigation (2)

Re: Dblink vs calling a function that returns void

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Boszormenyi Zoltan <zb(at)cybertec(dot)at>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Dblink vs calling a function that returns void
Date: 2010-03-30 16:24:45
Message-ID: b42b73151003300924u4d192a8ao99b168e2d07b2702@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
On Mon, Mar 29, 2010 at 12:12 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Boszormenyi Zoltan <zb(at)cybertec(dot)at> writes:
>> I need to call a function via dblink that returns a void, i.e.
>> technically nothing.
>
> You're overthinking the problem.  Imagine void is just a datatype
> (which it is...)  This should work:

but it isn't! void returning functions may not be queried over the
binary protocol (why?), so if you used dblink w/void returning
functions, and dblink later supported binary results, your code would
break (i'm sure such a thing would be optional, but the point stands).

merlin

In response to

Responses

pgsql-general by date

Next:From: Mike ToewsDate: 2010-03-30 16:29:52
Subject: Converting time interval to double precision of time unit
Previous:From: Joshua BerryDate: 2010-03-30 16:13:37
Subject: Re: User action accounting

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group