Re: charin(), text_char() should return something else for empty input - Mailing list pgsql-hackers

From Tom Lane
Subject Re: charin(), text_char() should return something else for empty input
Date
Msg-id 13894.991075052@sss.pgh.pa.us
Whole thread Raw
In response to charin(), text_char() should return something else for empty input  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: charin(), text_char() should return something else for empty input  (Don Baccus <dhogaza@pacifier.com>)
Re: Re: charin(), text_char() should return something else for empty input  (ncm@zembu.com (Nathan Myers))
List pgsql-hackers
I wrote:
> I propose that both of these operations should return a space character
> for an empty input string.  This is by analogy to space-padding as you'd
> get with char(1).  Any objections?

An alternative approach is to make charin and text_char map empty
strings to the null character (\0), and conversely make charout and
char_text map the null character to empty strings.  charout already
acts that way, in effect, since it has to produce a null-terminated
C string.  This way would have the advantage that there would still
be a reversible dump and reload representation for a "char" field
containing '\0', whereas space-padding would cause such a field to
become ' ' after reload.  But it's a little strange if you think that
"char" ought to behave the same as char(1).

Comments?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: doc markup bug....
Next
From: darcy@druid.net (D'Arcy J.M. Cain)
Date:
Subject: Re: New/old style trigger API