Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Pgsql Patches > Re: [BUGS] BUG ...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 1 of 3 Topic 3441 of 4253
Post > Topic >>

Re: [BUGS] BUG #4007: chr(0) doesn't work anymore

by bruce@[EMAIL PROTECTED] (Bruce Momjian) Mar 3, 2008 at 12:11 PM

--ELM1204564303-1879-0_
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"

Tom Lane wrote:
> Steve Clark <sclark@[EMAIL PROTECTED]
> writes:
> > I'm not sure I understand what you mean about TEXT being null-safe. 
> > What are the issues, and why was
> > it sup****ted for years and now abruptly changed.
> 
> It never was sup****ted, we are simply plugging a hole that let you
> create a text value that would be likely to malfunction in subsequent
> use.

Seems we never do***ented that chr(0) is not sup****ted.  I have applied
the following doc patch to CVS HEAD and 8.3.X.

-- 
  Bruce Momjian  <bruce@[EMAIL PROTECTED]
>        http://momjian.us
  EnterpriseDB                            
http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

--ELM1204564303-1879-0_
Content-Transfer-Encoding: 7bit
Content-Type: text/x-diff
Content-Disposition: inline; filename="/rtmp/diff"

Index: doc/src/sgml/func.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/func.sgml,v
retrieving revision 1.420
diff -c -c -r1.420 func.sgml
*** doc/src/sgml/func.sgml	26 Feb 2008 15:32:30 -0000	1.420
--- doc/src/sgml/func.sgml	3 Mar 2008 17:07:22 -0000
***************
*** 1340,1346 ****
          Character with the given code. For <acronym>UTF8</acronym> the
          argument is treated as a Unicode code point. For other multibyte
          encodings the argument must designate a strictly
!         <acronym>ASCII</acronym> character.
         </entry>
         <entry><literal>chr(65)</literal></entry>
         <entry><literal>A</literal></entry>
--- 1340,1347 ----
          Character with the given code. For <acronym>UTF8</acronym> the
          argument is treated as a Unicode code point. For other multibyte
          encodings the argument must designate a strictly
!         <acronym>ASCII</acronym> character.  The NULL (0) character is
not
!         allowed because text data types cannot reliably store such
bytes.
         </entry>
         <entry><literal>chr(65)</literal></entry>
         <entry><literal>A</literal></entry>

--ELM1204564303-1879-0_
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


--
Sent via pgsql-patches mailing list (pgsql-patches@[EMAIL PROTECTED]
)
To make changes to your Subscription:
http://mail.postgresql.org/mj/mj_wwwusr?domain=postgresql.org&extra=pgsql-patches

--ELM1204564303-1879-0_--
 




 3 Posts in Topic:
Re: [BUGS] BUG #4007: chr(0) doesn't work anymore
bruce@[EMAIL PROTECTED]   2008-03-03 12:11:43 
Re: [BUGS] BUG #4007: chr(0) doesn't work anymore
andrew@[EMAIL PROTECTED]   2008-03-03 13:02:57 
Re: [BUGS] BUG #4007: chr(0) doesn't work anymore
bruce@[EMAIL PROTECTED]   2008-03-03 13:09:10 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Fri Dec 5 6:26:39 CST 2008.