Skip site navigation (1) Skip section navigation (2)

Re: Re: charin(), text_char() should return something else for empty input

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: charin(), text_char() should return something else for empty input
Date: 2001-05-29 22:55:13
Message-ID: 20099.991176913@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> In general, I don't see a point in accepting a zero byte in character
> strings.  If you want to store binary data there are binary data types (or
> effort could be invested in them).

If we were starting in a green field then I'd think it worthwhile to
maintain null-byte-cleanness for the textual datatypes.  At this point,
though, the amount of pain involved seems to vastly outweigh the value.
The major problem is that I/O conventions not based on null-terminated
strings would break all existing user-defined datatypes.  (Changing our
own code is one thing, breaking users' code is something else.)  There
are minor-by-comparison problems like not being able to use strcoll()
for locale-sensitive comparisons anymore...

I agree with Peter that spending some extra effort on bytea and/or
similar types is probably a more profitable answer.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2001-05-30 00:54:33
Subject: Re: Proceeding with gettext
Previous:From: Peter EisentrautDate: 2001-05-29 21:20:47
Subject: Re: Re: charin(), text_char() should return something else for empty input

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group