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

Re: Escaping of special characters in ARRAYs is broken

From: Gerhard Häring <haering_linux(at)gmx(dot)de>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Escaping of special characters in ARRAYs is broken
Date: 2002-04-22 06:21:30
Message-ID: 20020422062130.GA7262@lilith.my-fqdn.de (view raw or flat)
Thread:
Lists: pgsql-bugs
* Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> [2002-04-21 11:12 -0400]:
> Gerhard =?iso-8859-15?Q?H=E4ring?= <haering_linux(at)gmx(dot)de> writes:
> > You can see the inconsistency yourself when you try to insert a special
> > character like \005 into a varchar array. IMO This should work with inserting
> > '{"\\005"}', but this just inserts the three letters 005.
> 
> This is not a bug; you didn't use enough backslashes.  See the example
> at the bottom of this page:
> http://candle.pha.pa.us/main/writings/pgsql/sgml/arrays.html
 
Thanks. The bug was elsewhere: in the client library I use. I fixed this
in the meantime. The CVS version of pyPgSQL now supports ARRAYs and even
multidimensional ARRAYs.

Gerhard
-- 
mail:   gerhard <at> bigfoot <dot> de       registered Linux user #64239
web:    http://www.cs.fhm.edu/~ifw00065/    OpenPGP public key id AD24C930
public key fingerprint: 3FCC 8700 3012 0A9E B0C9  3667 814B 9CAA AD24 C930
reduce(lambda x,y:x+y,map(lambda x:chr(ord(x)^42),tuple('zS^BED\nX_FOY\x0b')))

In response to

pgsql-bugs by date

Next:From: pgsql-bugsDate: 2002-04-22 12:21:20
Subject: Bug #638: Buggy select statment with numeric
Previous:From: Ian MorganDate: 2002-04-22 06:07:39
Subject: 7.2.1: pg_dump of UNIONed VIEWs broken

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