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

From David G. Johnston
Subject Re: Moving from PHP to Java: A result was returned when none was expected.
Date
Msg-id CAKFQuwZM6VaiuEGx9=kNnpninhGNechh0QPXXKA8m=rFcsQeVw@mail.gmail.com
Whole thread Raw
In response to Re: Moving from PHP to Java: A result was returned when none was expected.  (Jan de Visser <jan@de-visser.net>)
Responses Re: Moving from PHP to Java: A result was returned when none was expected.
Re: Moving from PHP to Java: A result was returned when none was expected.
List pgsql-general
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.

​David J.​

pgsql-general by date:

Previous
From: Jan de Visser
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.