1berry/MariaDB-server
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarification of UNIX_TIMESTAMP() limited range checking.

Browse Source
This commit is contained in:
unknown 2002-05-21 10:04:34 +10:00
parent 806c5aab9e
commit 61830734c3
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
Docs/manual.texi
View File

@ -32499,8 +32499,9 @@ mysql> SELECT UNIX_TIMESTAMP('1997-10-04 22:23:00');
When @code{UNIX_TIMESTAMP} is used on a @code{TIMESTAMP} column, the function When @code{UNIX_TIMESTAMP} is used on a @code{TIMESTAMP} column, the function
will return the internal timestamp value directly, with no implicit will return the internal timestamp value directly, with no implicit
``string-to-unix-timestamp'' conversion. ``string-to-unix-timestamp'' conversion.
If you give @code{UNIX_TIMESTAMP()} a wrong or out-of-range date, it will If you pass an out-of-range date to @code{UNIX_TIMESTAMP()} it will
return 0. return 0, but please note that only basic checking is performed
(year 1970-2037, month 01-12, day 01-31).
If you want to subtract @code{UNIX_TIMESTAMP()} columns, you may want to If you want to subtract @code{UNIX_TIMESTAMP()} columns, you may want to
cast the result to signed integers. @xref{Cast Functions}. cast the result to signed integers. @xref{Cast Functions}.