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

On Fri, Feb 19, 2010 at 09:18, Alex Hunsaker <badalex@gmail.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. =C2=A0Then again, no one has complained thus far... =C2=
=A0Maybe
> 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.