Simon Riggs wrote:
>> - I think that every feature of the line protocol should
>> be exposed in the C API.
>
> Exposing every possible bug in ther underlying protocol isn't the best
> plan though, especially when doing so complicates the API just to
> support this.
Well, I wouldn't call this a
Simon Riggs writes:
> On 7 November 2012 13:08, Albe Laurenz wrote:
>> - I think that every feature of the line protocol should
>> be exposed in the C API.
My recollection is that there are several things in the V3 protocol that
were put there to satisfy JDBC, without any expectation that they'd
On Wed, Nov 7, 2012 at 7:08 AM, Albe Laurenz wrote:
> The Frontend/Backend protocol's "bind" message allows to
> specify mixed text and binary result formats, but there
> is not support in the C API for that.
>
> I'd like to add support for that to libpq for these reasons:
>
> - I think that every
On 7 November 2012 13:08, Albe Laurenz wrote:
> - I think that every feature of the line protocol should
> be exposed in the C API.
Exposing every possible bug in ther underlying protocol isn't the best
plan though, especially when doing so complicates the API just to
support this.
Are those
The Frontend/Backend protocol's "bind" message allows to
specify mixed text and binary result formats, but there
is not support in the C API for that.
I'd like to add support for that to libpq for these reasons:
- I think that every feature of the line protocol should
be exposed in the C API.
