Re: BUG #5334: Version 2.22 of Perl Safe module breaks UTF8 PostgreSQL 8.4

From: Alex Hunsaker <badalex(at)gmail(dot)com>
To: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5334: Version 2.22 of Perl Safe module breaks UTF8 PostgreSQL 8.4
Date: 2010-02-19 16:32:38
Message-ID: 34d269d41002190832p569ebba6t78a3c6e9d2408693@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Feb 19, 2010 at 09:18, Alex Hunsaker <badalex(at)gmail(dot)com> wrote:
> It seems to me a more correct fix would be to require utf8; inside of
> the safe like we do strict.
> ....
> Id favor this approach as if you have utf8 strings the likely hood
> that you want ::upgrade, ::downgrade, ::encode, ::valid or ::is_utf8
> is fairly high.  Then again, no one has complained thus far...  Maybe
> thats just me :)

On second thought, I dont think we should import any of those by
default. And your hack for just SWASHNEW is better.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David E. Wheeler 2010-02-19 17:00:59 Re: [Tigerlead] BUG #5334: Version 2.22 of Perl Safe module breaks UTF8 PostgreSQL 8.4
Previous Message Alex Hunsaker 2010-02-19 16:30:08 Re: BUG #5334: Version 2.22 of Perl Safe module breaks UTF8 PostgreSQL 8.4