Adding nullable indicator to Describe - Mailing list pgsql-hackers

From Chris Forno
Subject Adding nullable indicator to Describe
Date
Msg-id AANLkTimU-HUqikGxgu1Tv0a3wJu4P2WndEuSDAXPk70i@mail.gmail.com
Whole thread Raw
Responses Re: Adding nullable indicator to Describe
List pgsql-hackers
I'd like to add information about whether or not a parameter or result can potentially be NULL to the RowDescription
message.<br/><br />Reason: I have the same reasons that Richard Jones did in 2006 (<a
href="http://archives.postgresql.org/pgsql-interfaces/2006-01/msg00043.php">http://archives.postgresql.org/pgsql-interfaces/2006-01/msg00043.php</a>).
I'mwriting a Haskell library that derives the types of the result at compile-time. For nullable columns, it needs to
knowin advance to wrap the type in the Maybe monad. Looking at the table column information is great, but I'd like to
supportthe case where a function is used in the SELECT (among any other potential cases).<br /><br />I'm new to the
codebase. Can you point me in the right direction?<br /><br />I'd like to add the indicator without making the protocol
backwards-incompatible.My first thought was to use a bit in the type modifier field, but that doesn't seem safe. Any
suggestions?<br/><br /><br /> 

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Per-column collation
Next
From: Tom Lane
Date:
Subject: Re: Adding nullable indicator to Describe