Thread: Re: [HACKERS] Re: [INTERFACES] retrieving varchar size

>> The JDBC spec allows for multiple ResultSet's to be returned from a query,
>> and our driver handles this already.
>
>Oh.  That prevents us from changing the backend to ignore returning more
>than one result for multiple queries in a PQexec.

I think this is also a leftover from postgres 4.2, where one query could return multiple
result sets (with different columns).

>Perhaps we need a new
>return query protocol character like 'J' to denote query returns that
>are not the LAST return, so libpq can throw them away, and jdbc and
>process them as normal, but also figure out when it gets the last one.

This might be hard to do with a select rule, that triggers other result sets.
(Is this still possible ?)

Andreas

>
> >> The JDBC spec allows for multiple ResultSet's to be returned from a query,
> >> and our driver handles this already.
> >
> >Oh.  That prevents us from changing the backend to ignore returning more
> >than one result for multiple queries in a PQexec.
>
> I think this is also a leftover from postgres 4.2, where one query could return multiple
> result sets (with different columns).
>
> >Perhaps we need a new
> >return query protocol character like 'J' to denote query returns that
> >are not the LAST return, so libpq can throw them away, and jdbc and
> >process them as normal, but also figure out when it gets the last one.
>
> This might be hard to do with a select rule, that triggers other result sets.
> (Is this still possible ?)

We are going to use a separate end-of-query-results packet instead.

--
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)