Tom Lane wrote:
> "Heikki Linnakangas" <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> This risk seems rather overstated, as it's unlikely that someone using
> >> money would choose to reload their data into a DB with a fundamentally
> >> incompatible locale setting.
>
> > It doesn't sound
"Heikki Linnakangas" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> This risk seems rather overstated, as it's unlikely that someone using
>> money would choose to reload their data into a DB with a fundamentally
>> incompatible locale setting.
> It doesn't sound unlikely at all to me. For exa
Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
>> Since the money type has a locale dependent input and output format, there
>> has
>> to be some context saved when a database dump is created. For example, if
>> your environment uses a locale that uses the opposite point-vs-comm
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Since the money type has a locale dependent input and output format, there
> has
> to be some context saved when a database dump is created. For example, if
> your environment uses a locale that uses the opposite point-vs-comma
> conventions from
Since the money type has a locale dependent input and output format, there has
to be some context saved when a database dump is created. For example, if
your environment uses a locale that uses the opposite point-vs-comma
conventions from English (e.g., de_DE), then the following will fail to
