Re: Moving from PHP to Java: A result was returned when none was expected. - Mailing list pgsql-general

From Jan de Visser
Subject Re: Moving from PHP to Java: A result was returned when none was expected.
Date
Msg-id 3335632.u4xMSDsk2z@coyote
Whole thread Raw
In response to Re: Moving from PHP to Java: A result was returned when none was expected.  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
On Wednesday, June 15, 2016 10:43:13 AM EDT David G. Johnston wrote:
> On Wed, Jun 15, 2016 at 10:30 AM, Jan de Visser <jan@de-visser.net> wrote:
> > Point is that you're doing a SELECT. A SELECT returns a result, which can
> > be
> > empty. I would use executeQuery and ignore the result.
> >
> > There is a bit of a mismatch between the JDBC stored procedure model and
> > the
> > pgsql function model, because pgsql doesn't have true stored procedures.
>
> Can you point to docs, JDBC and/or PG, that describe what it means to
> "RETURN void"?
>
> At a high-level SQL returns SETs and the empty set is a valid SET.  I take
> it from your comment that JDBC considers the empty set "a result", whose
> record count is zero.

That's what I assume.





pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Moving from PHP to Java: A result was returned when none was expected.
Next
From: Jan de Visser
Date:
Subject: Re: Moving from PHP to Java: A result was returned when none was expected.