On Fri, Feb 19, 2010 at 09:32:38AM -0700, Alex Hunsaker wrote: > On Fri, Feb 19, 2010 at 09:18, Alex Hunsaker <bada...@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. 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.
Here's the corresponding perlbug http://rt.perl.org/rt3/Ticket/Display.html?id=72942 I'll retest 8.4 and 9.0 against this on Monday. Tim. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
