Re: Unexpected behaviour of encode()

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Bill Moran <wmoran(at)potentialtech(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Unexpected behaviour of encode()
Date: 2013-03-26 18:17:27
Message-ID: CAHyXU0z2b1RGaUwJxhJ_znWCZkNQo=6ht2qB1zjyd3ekc_UatA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Mar 26, 2013 at 12:47 PM, Bill Moran <wmoran(at)potentialtech(dot)com> wrote:
>
> 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.

why? that isn't what you passed it. the input string doubled single
quotes is converted to single single quote per spec. it's 'ghetto
escaping'.

merlin

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Grittner 2013-03-26 18:28:54 Re: pg_stat_get_last_vacuum_time(): why non-FULL?
Previous Message Bill Moran 2013-03-26 17:47:30 Unexpected behaviour of encode()