Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id KAA39352;
	Mon, 6 Dec 1999 10:23:03 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA18451;
	Mon, 6 Dec 1999 10:22:32 -0500 (EST)
To: Michael Meskes <meskes@postgreSQL.org>
cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Spanish format on date and numbers 
In-reply-to: Your message of Mon, 6 Dec 1999 07:54:42 +0100
	<19991206075442.A1392@fam-meskes.de>
Date: Mon, 06 Dec 1999 10:22:32 -0500
Message-ID: <18449.944493752@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Michael Meskes <meskes@postgreSQL.org> writes:
> On Mon, Dec 06, 1999 at 02:02:15AM +0000, Thomas Lockhart wrote:
>> I haven't tested this, but we do use the system libraries for reading
>> numbers. So if they are locale-enabled, then locale-specific numbers
>> should be recognized...

> Yes, but the parser probably won't. It definitely only lists a decimal
> point.

We can't mess around with SQL syntax --- or would you like

	SELECT 12,34;

to have locale-dependent results?

However, I think we could make the type-specific I/O routines for
appropriate types be locale-dependent.  So you could do

	SELECT '12,34'::int4;

and get the desired behavior in a locale where , is the radix point.

OTOH, arrays of int might be tricky...

			regards, tom lane