I can't remember anyone asking for more sophisticated
solutions so it seems implementing #1 at this point is the
best approach.
OK. Then I'll start working on the first approach.
Regards,
Gevik.
---(end of broadcast)---
TIP 7: You can
Gevik Babakhani wrote:
Surely it should be the inverse of the solution for output,
eg TMMon selects localized input.
After some investigation in how gettext works, I would like to have your
opinion about how to
implement this TODO item.
Starting with TO_CHAR:
When the TM
] TODO item:Allow to_date() and
to_timestamp() accept localized month names
Alvaro Herrera wrote:
Nevertheless, I think there's something interesting missing here,
which is a sort of strftime's %c format string.
I think the Oracle way to do that would be to_char() with one
argument
@postgresql.org
Subject: Re: [HACKERS] TODO item:Allow to_date() and
to_timestamp() accept localized month names
Gevik Babakhani [EMAIL PROTECTED] writes:
Surely it should be the inverse of the solution for
output, eg TMMon
selects localized input.
Of cource. But how would TM enforce
Gevik Babakhani [EMAIL PROTECTED] writes:
What do we think about a solution that would be like:
1. Add an extra (optional) parameter to to_date and to_timestamp which would
indicate the locale we are trying to parse.
Surely it should be the inverse of the solution for output, eg TMMon
Hi,
I would like to start a discussion for a solution regarding this item.
At this moment these functions only accept English month/day names due
formatting.c:172:months_full[] and datetime.c:53-58 months[], days[].
The values are predetermined. (hardcoded sounds bahhh...)
What do we think
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
Gevik Babakhani [EMAIL PROTECTED] 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
Tom Lane wrote:
Gevik Babakhani [EMAIL PROTECTED] 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
Alvaro Herrera [EMAIL PROTECTED] writes:
Nevertheless, I think there's something interesting missing here, which
is a sort of strftime's %c format string.
Perhaps, but let us please not cram random non-Oracle-compatible stuff
into to_date/to_char. Those have a charter already.
10 matches
Mail list logo
