(I really should stop reading the code after 12:00AM)
So if I understand correctly, the proper solution would be to handle the
localized (TM) format
within to_date (seq_search). This means that prior calling to_date a SET
LC_MESSAGES must be given.
but if we are following Oracle,
(http://www.techonthenet.com/oracle/functions/to_date.php) a third parameter
to enforce the nls_language is required. Please advice.
Regards,
Gevik.
> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Tuesday, February 05, 2008 2:29 AM
> To: Gevik Babakhani
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] TODO item:Allow to_date() and
> to_timestamp() accept localized month names
>
> "Gevik Babakhani" <pgdev@xs4all.nl> writes:
> >> Surely it should be the inverse of the solution for
> output, eg TMMon
> >> selects localized input.
>
> > Of cource. But how would TM enforce a localized formatting.
> (perhaps I
> > am off.... 2:10 am...) Lets say I have en_US database but
> the dates I
> > am trying to format is nl_NL.
> > If I am not mistaking SET LC_MESSAGES won't help.
>
> Works for me:
>
> postgres=# show lc_messages ;
> lc_messages
> -------------
> de_DE.utf8
> (1 row)
>
> postgres=# select to_char(now(), 'TMDay, DD TMMonth YYYY');
> to_char
> -------------------------
> Montag, 04 Februar 2008
> (1 row)
>
> postgres=# set lc_messages TO 'es_ES.utf8'; SET postgres=#
> select to_char(now(), 'TMDay, DD TMMonth YYYY');
> to_char
> ------------------------
> Lunes, 04 Febrero 2008
> (1 row)
>
>
> regards, tom lane
>
