[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] Problems with pgcrypto and special characters
From:       "Markus Wollny" <Markus.Wollny () computec ! de>
Date:       2005-02-28 21:00:32
Message-ID: 2266D0630E43BB4290742247C891057502B9D6E3 () dozer ! computec ! de
[Download RAW message or body]

Hi!

-----Original Message-----
From:	Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Possibly a binary cast (WITHOUT FUNCTION) would solve your problem,
> though I doubt it will work well on bytea values containing \0.

Thanks, I've been a bit thick here, but I just found the solution to my problem - and \
that doesn't need this awkward function nor any type of extra WITHOUT FUNCTION casts \
- just decode and encode, alas in exactly the opposite order than I originally \
expected.

mypgdb=# select decode('Tübingen'::text,'escape');
     decode
-----------------
 T\303\274bingen
(1 row)

mypgdbe=# select encode('T\303\274bingen','escape');
  encode
----------
 Tübingen
(1 row)

I think this should be safe for any kind of bytea value.

Kind regards

   Markus


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match


[prev in list] [next in list] [prev in thread] [next in thread]