From: | Chris Forno <chris(at)forno(dot)us> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Adding nullable indicator to Describe |
Date: | 2010-11-17 05:01:57 |
Message-ID: | [email protected] |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I'd like to add information about whether or not a parameter or result can
potentially be NULL to the RowDescription message.
Reason: I have the same reasons that Richard Jones did in 2006 (
http://archives.postgresql.org/pgsql-interfaces/2006-01/msg00043.php) I'm
writing a Haskell library that derives the types of the result at
compile-time. For nullable columns, it needs to know in advance to wrap the
type in the Maybe monad. Looking at the table column information is great,
but I'd like to support the case where a function is used in the SELECT
(among any other potential cases).
I'm new to the code base. Can you point me in the right direction?
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?
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2010-11-17 05:07:33 | Re: Per-column collation |
Previous Message | Robert Haas | 2010-11-17 02:41:37 | Re: contrib: auth_delay module |