On 10-8-2013 15:03, Dmitry Yemanov wrote:
> 10.08.2013 16:15, Mark Rotteveel wrote:
>>
>> I am still wondering though if it shouldn't actually be using xdr_bool
>> instead of xdr_opaque.
>
> For byte streams (and CHAR[1] can be surely considered a byte stream)
> xdr_opaque is a correct choice. BTW,
10.08.2013 16:15, Mark Rotteveel wrote:
>
> I am still wondering though if it shouldn't actually be using xdr_bool
> instead of xdr_opaque.
For byte streams (and CHAR[1] can be surely considered a byte stream)
xdr_opaque is a correct choice. BTW, I failed to find xdr_bool in trunk,
perhars it wa
On 10-8-2013 08:36, Mark Rotteveel wrote:
> Anyone?
>
> On 8-8-2013 19:10, Mark Rotteveel wrote:
>> I was looking at implementing boolean in Jaybird trunk (+ backport to
>> 2.2.x), but I'd like some confirmation on how it is encoded in the
>> XSQLVAR and in the wireprotocol.
>>
>> A quick skim of t
Anyone?
On 8-8-2013 19:10, Mark Rotteveel wrote:
> I was looking at implementing boolean in Jaybird trunk (+ backport to
> 2.2.x), but I'd like some confirmation on how it is encoded in the
> XSQLVAR and in the wireprotocol.
>
> A quick skim of the sources seem to indicate that the XSQLVAR sqldata
I was looking at implementing boolean in Jaybird trunk (+ backport to
2.2.x), but I'd like some confirmation on how it is encoded in the
XSQLVAR and in the wireprotocol.
A quick skim of the sources seem to indicate that the XSQLVAR sqldata is
a single byte. And that 0x00 is considered false and
