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

manual.texi fix for colons in TIME being referred to as semicolons

Browse Source
This commit is contained in:
paul@teton.kitebird.com 2002-01-17 16:22:54 -06:00
parent 01d6d4ae19
commit 73942d8953
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Docs/manual.texi
View File

@ -28935,14 +28935,14 @@ seconds values that are less than @code{10}. @code{'8:3:2'} is the same as
@code{'08:03:02'}. @code{'08:03:02'}.
Be careful about assigning ``short'' @code{TIME} values to a @code{TIME} Be careful about assigning ``short'' @code{TIME} values to a @code{TIME}
column. Without semicolon, MySQL interprets values using the column. Without colons, MySQL interprets values using the
assumption that the rightmost digits represent seconds. (MySQL assumption that the rightmost digits represent seconds. (MySQL
interprets @code{TIME} values as elapsed time rather than as time of interprets @code{TIME} values as elapsed time rather than as time of
day.) For example, you might think of @code{'1112'} and @code{1112} as day.) For example, you might think of @code{'1112'} and @code{1112} as
meaning @code{'11:12:00'} (12 minutes after 11 o'clock), but meaning @code{'11:12:00'} (12 minutes after 11 o'clock), but
MySQL interprets them as @code{'00:11:12'} (11 minutes, 12 seconds). MySQL interprets them as @code{'00:11:12'} (11 minutes, 12 seconds).
Similarly, @code{'12'} and @code{12} are interpreted as @code{'00:00:12'}. Similarly, @code{'12'} and @code{12} are interpreted as @code{'00:00:12'}.
@code{TIME} values with semicolon, instead, are always treated as @code{TIME} values with colons, by contrast, are always treated as
time of the day. That is @code{'11:12'} will mean @code{'11:12:00'}, time of the day. That is @code{'11:12'} will mean @code{'11:12:00'},
not @code{'00:11:12'}. not @code{'00:11:12'}.