Re: Strange results from to_timestamp
От | Mario Weilguni |
---|---|
Тема | Re: Strange results from to_timestamp |
Дата | |
Msg-id | FA095C015271B64E99B197937712FD020E4B090F@freedom.grz.icomedias.com обсуждение исходный текст |
Ответ на | Strange results from to_timestamp (Mario Weilguni <mweilguni@sime.com>) |
Ответы |
Re: Strange results from to_timestamp
|
Список | pgsql-hackers |
to_timestamp is only for Oracle compatibility? I always thought it's some sort of sql standard. What's the sql compliantway to do this? Regards, mario weilguni -----Ursprüngliche Nachricht----- Von: pgsql-hackers-owner@postgresql.org [mailto:pgsql-hackers-owner@postgresql.org] Im Auftrag von Tom Lane Gesendet: Freitag, 07. April 2006 06:09 An: Mario Weilguni Cc: PostgreSQL-development Betreff: Re: [HACKERS] Strange results from to_timestamp Mario Weilguni <mweilguni@sime.com> writes: > I think all except the first one should raise a warning, isn't it? to_timestamp (and friends) all seem to me to act pretty bizarre when faced with input that doesn't match the given formatstring. However, in the end that is an Oracle-compatibility function, and there is only one measure of what it shoulddo: what does Oracle do in the same case. Can anyone try these examples on a recent Oracle version? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
В списке pgsql-hackers по дате отправления: