Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
mariadb
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
mariadb
Commits
90c5ac46
Commit
90c5ac46
authored
Jun 27, 2002
by
unknown
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Clarification of legal database/table/column names.
Clarification of NOW() behaviour.
parent
d1c1de71
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
1 deletion
+7
-1
Docs/manual.texi
Docs/manual.texi
+7
-1
No files found.
Docs/manual.texi
View file @
90c5ac46
...
...
@@ -28310,7 +28310,9 @@ you must always quote it with @code{`} when you use it:
mysql> SELECT * FROM `select` WHERE `select`.id > 100;
@end example
In previous versions of MySQL, the name rules are as follows:
@xref{Reserved words}.
In MySQL versions prior to 3.23.6, the name rules are as follows:
@itemize @bullet
@item
...
...
@@ -32604,6 +32606,10 @@ mysql> SELECT NOW() + 0;
-> 19971215235026
@end example
Note that @code{NOW()} is only evaluated once per query, namely at the
start of query execution. This means that multiple references to
@code{NOW()} within a single query will always give the same time.
@findex UNIX_TIMESTAMP()
@item UNIX_TIMESTAMP()
@itemx UNIX_TIMESTAMP(date)
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment