On Thu, 11 Jun 2020 at 15:07, Shay Rojansky wrote:
>
> > Second, across the protocol docs, rather than using Int32 and Int64,
>> which
>> > generally look like they're signed (depending on which language you're
>> > coming from), I'd consider using UInt32/UInt64, which are unambiguous
>> with
>>
> > Second, across the protocol docs, rather than using Int32 and Int64,
> which
> > generally look like they're signed (depending on which language you're
> > coming from), I'd consider using UInt32/UInt64, which are unambiguous
> with
> > regards to signed-ness.
>
> Well, they are actually signed
On 2020-06-09 23:35, PG Doc comments form wrote:
The protocol docs generally do not mention whether ints are signed or
unsigned - this has actually bitten me once in the past, where a signed int
was accidentally used to interpret an unsigned int coming from PostgreSQL,
leading to issues. The ambi
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/protocol-message-types.html
Description:
Hi, I'm the maintainer of Npgsql, the .NET open source driver for
PostgreSQL.
The protocol docs generally do not mention whether ints are signed o
