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

Re: Making TEXT NUL-transparent

From: Alexander Shulgin <ash(at)commandprompt(dot)com>
To: Florian Weimer <fweimer(at)bfk(dot)de>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Making TEXT NUL-transparent
Date: 2011-11-24 09:35:02
Message-ID: 1322127105-sup-5764@moon (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Excerpts from Florian Weimer's message of Thu Nov 24 11:27:51 +0200 2011:
> > and why you don't use bytea ? Text should be correct literal.
> It's actually UTF-8 text, and some PostgreSQL functions are only
> available for TEXT, but not BYTEA, e.g.:
> bfk_int=> SELECT '\x006500'::bytea ~ 'A';
> ERROR:  operator does not exist: bytea ~ unknown

And how will those TEXT functions behave on a value with an embedded NUL?  Or is it not only about being able to *store* NULs in a text field?


In response to


pgsql-hackers by date

Next:From: Lars KanisDate: 2011-11-24 09:39:07
Subject: Re: [PATCH] PostgreSQL fails to build with 32bit MinGW-w64
Previous:From: Florian WeimerDate: 2011-11-24 09:27:51
Subject: Re: Making TEXT NUL-transparent

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