Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Michael Paesold <mpaesold(at)gmx(dot)at>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)
Date: 2006-01-09 05:39:30
Message-ID: 87r77i0xkd.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > The attached patch against cvs tip does seem to work. Instead of playing
> > with the environment, we simply allow perl to do its worst and then put
> > things back the way we wanted them.

How does that affect to the API calls you can make from Perl back into the
database? What if you change the locale and then issue a query from within
Perl?

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stefan Kaltenbrunner 2006-01-09 07:55:06 Re: Fw: Is anyone interested in getting PostgreSQL working
Previous Message Tom Lane 2006-01-09 04:56:52 Re: plpgsql: check domain constraints