Commite2224fa

committed

docs: to_timestamp and to_date do minimal range checking

Initial patch from Steve Crawford

1 parentb44fc39 commite2224faCopy full SHA for e2224fa

File tree

+14

-0

lines changed

+14

-0

lines changed

Lines changed: 14 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -5783,6 +5783,20 @@ SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})');`
`5783`	`5783`	`</para>`
`5784`	`5784`	`</listitem>`
`5785`	`5785`
	`5786`	`+ <listitem>`
	`5787`	`+ <para>`
	`5788`	`+ <function>to_timestamp</function> and <function>to_date</function>`
	`5789`	`+ exist to handle input formats that cannot be converted by`
	`5790`	`+ simple casting. These functions interpret input liberally,`
	`5791`	`+ with minimal error checking. While they produce valid output,`
	`5792`	`+ the conversion can yield unexpected results. For example,`
	`5793`	`+ input to these functions is not restricted by normal ranges,`
	`5794`	`+ thus <literal>to_date('20096040','YYYYMMDD')</literal> returns`
	`5795`	`+ <literal>2014-01-17</literal> rather than causing an error.`
	`5796`	`+ Casting does not have this behavior.`
	`5797`	`+ </para>`
	`5798`	`+ </listitem>`
	`5799`	`+`
`5786`	`5800`	`<listitem>`
`5787`	`5801`	`<para>`
`5788`	`5802`	`Ordinary text is allowed in <function>to_char</function>`

Comments

(0)