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
d45bf758
Commit
d45bf758
authored
Sep 26, 2001
by
serg@serg.mysql.com
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
manual cleanups
parent
3b774da4
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
16 additions
and
14 deletions
+16
-14
BitKeeper/etc/logging_ok
BitKeeper/etc/logging_ok
+1
-0
Docs/manual.texi
Docs/manual.texi
+15
-14
No files found.
BitKeeper/etc/logging_ok
View file @
d45bf758
Miguel@light.local
Miguel@light.local
serg@serg.mysql.com
Docs/manual.texi
View file @
d45bf758
...
@@ -30991,7 +30991,8 @@ mysql> select ATAN(-2);
...
@@ -30991,7 +30991,8 @@ mysql> select ATAN(-2);
@end example
@end example
@findex ATAN2()
@findex ATAN2()
@item ATAN2(Y,X)
@item ATAN(Y,X)
@itemx ATAN2(Y,X)
Returns the arc tangent of the two variables @code{X} and @code{Y}. It is
Returns the arc tangent of the two variables @code{X} and @code{Y}. It is
similar to calculating the arc tangent of @code{Y / X}, except that the
similar to calculating the arc tangent of @code{Y / X}, except that the
signs of both arguments are used to determine the quadrant of the
signs of both arguments are used to determine the quadrant of the
...
@@ -30999,7 +31000,7 @@ result:
...
@@ -30999,7 +31000,7 @@ result:
@example
@example
mysql> select ATAN(-2,2);
mysql> select ATAN(-2,2);
-> -0.785398
-> -0.785398
mysql> select ATAN(PI(),0);
mysql> select ATAN
2
(PI(),0);
-> 1.570796
-> 1.570796
@end example
@end example
...
@@ -32203,6 +32204,18 @@ MySQL will directly use disk-based temporary tables if needed.
...
@@ -32203,6 +32204,18 @@ MySQL will directly use disk-based temporary tables if needed.
MySQL will also, in this case, prefer sorting to doing a
MySQL will also, in this case, prefer sorting to doing a
temporary table with a key on the @code{GROUP BY} elements.
temporary table with a key on the @code{GROUP BY} elements.
@item
@code{SQL_BUFFER_RESULT} will force the result to be put into a temporary
table. This will help MySQL free the table locks early and will help
in cases where it takes a long time to send the result set to the client.
@item
@code{SQL_SMALL_RESULT}, a MySQL-specific option, can be used
with @code{GROUP BY} or @code{DISTINCT} to tell the optimizer that the
result set will be small. In this case, MySQL will use fast
temporary tables to store the resulting table instead of using sorting. In
MySQL Version 3.23 this shouldn't normally be needed.
@item
@item
@cindex @code{GROUP BY}, extensions to ANSI SQL
@cindex @code{GROUP BY}, extensions to ANSI SQL
If you use @code{GROUP BY}, the output rows will be sorted according to the
If you use @code{GROUP BY}, the output rows will be sorted according to the
...
@@ -32221,18 +32234,6 @@ If you are not getting the results you expect from your query, please
...
@@ -32221,18 +32234,6 @@ If you are not getting the results you expect from your query, please
read the @code{GROUP BY} description.
read the @code{GROUP BY} description.
@xref{Group by functions}.
@xref{Group by functions}.
@item
@code{SQL_BUFFER_RESULT} will force the result to be put into a temporary
table. This will help MySQL free the table locks early and will help
in cases where it takes a long time to send the result set to the client.
@item
@code{SQL_SMALL_RESULT}, a MySQL-specific option, can be used
with @code{GROUP BY} or @code{DISTINCT} to tell the optimizer that the
result set will be small. In this case, MySQL will use fast
temporary tables to store the resulting table instead of using sorting. In
MySQL Version 3.23 this shouldn't normally be needed.
@item
@item
@code{STRAIGHT_JOIN} forces the optimizer to join the tables in the order in
@code{STRAIGHT_JOIN} forces the optimizer to join the tables in the order in
which they are listed in the @code{FROM} clause. You can use this to speed up
which they are listed in the @code{FROM} clause. You can use this to speed up
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