| From: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
|---|---|
| To: | bob(dot)rumsby(at)yahoo(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: FX modifier |
| Date: | 2018-06-19 18:11:15 |
| Message-ID: | CAHE3wggsRC0rytfuqR7w=_pQCGB4zBGXMf4ecj=SL5_JSa50-A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
2018-06-14 17:16 GMT-03:00 PG Doc comments form <noreply(at)postgresql(dot)org>:
> The FX modifier is defined only as "fixed format global option"--what does
> this mean?
> The usage notes do not mention FX for TO_CHAR. Does it work with TO_CHAR?
>
This is not a bug. The documentation is clear.
"to_timestamp and to_date skip multiple blank spaces in the input
string unless the FX option is used. For example, to_timestamp('2000
JUN', 'YYYY MON') works, but to_timestamp('2000 JUN', 'FXYYYY
MON') returns an error because to_timestamp expects one space only. FX
must be specified as the first item in the template."
FX only applies to to_timestamp and to_date.
--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Euler Taveira | 2018-06-19 18:39:42 | Re: postgresql 11 release notes |
| Previous Message | Bruce Momjian | 2018-06-19 17:43:54 | Re: json_to_record Example |