Unexpected behaviour of encode()

From: Bill Moran <wmoran(at)potentialtech(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Unexpected behaviour of encode()
Date: 2013-03-26 17:47:30
Message-ID: 20130326134730.c82b3402d8443fa7006295b2@potentialtech.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


psql -U postgres
psql (9.2.3)
Type "help" for help.

postgres=# select encode('can''t', 'escape');
encode
--------
can't
(1 row)

I observed the same behaviour on one of our older systems (8.3.11) as well.

Am I missing something? I expected "can''t" as the output.

--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2013-03-26 18:17:27 Re: Unexpected behaviour of encode()
Previous Message Alban Hertroys 2013-03-26 16:17:36 Re: Why does Postgres allow duplicate (FK) constraints