Re: I/O support for composite types - Mailing list pgsql-hackers

From Tom Lane
Subject Re: I/O support for composite types
Date
Msg-id 29859.1086462931@sss.pgh.pa.us
Whole thread Raw
In response to Re: I/O support for composite types  (Thomas Hallgren <thhal@mailblocks.com>)
Responses Re: I/O support for composite types  (Thomas Hallgren <thhal@mailblocks.com>)
List pgsql-hackers
Thomas Hallgren <thhal@mailblocks.com> writes:
> Why not use standard C semantics for the textual representation with 
> your addition that empty items are NULL?

This isn't C, it's SQL; and I think the array I/O representation is a
closer precedent for us than the C standard.

In any case, how much of C syntax are you proposing to emulate exactly?
Comments?  Backslashed newlines?  Joining of adjacent double-quoted
strings?  Conversion of octal and hex integer constants (and what about
L, U, LL, etc suffixes)?  There's a lot more stuff there than meets the
eye, and most of it isn't something I want to code.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Thomas Hallgren
Date:
Subject: Re: I/O support for composite types
Next
From: elein
Date:
Subject: Re: I/O support for composite types