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
c2577b4d
Commit
c2577b4d
authored
Jun 14, 2002
by
unknown
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fixed one inconsistency in previous priv-names style edit.
Fix some grammatical errors using 's instead of s for plural.
parent
22bb27ce
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
8 deletions
+8
-8
Docs/manual.texi
Docs/manual.texi
+8
-8
No files found.
Docs/manual.texi
View file @
c2577b4d
...
@@ -8157,7 +8157,7 @@ To get these new privileges to work, one must run the
...
@@ -8157,7 +8157,7 @@ To get these new privileges to work, one must run the
users have the @strong{show databases}, @strong{create temporary tables},
users have the @strong{show databases}, @strong{create temporary tables},
and @strong{lock tables} privileges. @strong{super} and @strong{execute}
and @strong{lock tables} privileges. @strong{super} and @strong{execute}
privileges take their value from @strong{process}.
privileges take their value from @strong{process}.
@strong{replication slave} and @
code
{replication client} take their
@strong{replication slave} and @
strong
{replication client} take their
values from @strong{file}.
values from @strong{file}.
If you have any scripts that creates new users, you may want to change
If you have any scripts that creates new users, you may want to change
...
@@ -22166,7 +22166,7 @@ UPDATE table_name SET not_key_column=# WHERE not_key_column=# LIMIT 1;
...
@@ -22166,7 +22166,7 @@ UPDATE table_name SET not_key_column=# WHERE not_key_column=# LIMIT 1;
@item
@item
All big results are automatically limited to @code{#select_limit#} rows.
All big results are automatically limited to @code{#select_limit#} rows.
@item
@item
@code{SELECT}
'
s that will probably need to examine more than
@code{SELECT}s that will probably need to examine more than
@code{#max_join_size} row combinations will be aborted.
@code{#max_join_size} row combinations will be aborted.
@end itemize
@end itemize
...
@@ -25995,7 +25995,7 @@ as soon as it finds @code{#} unique rows.
...
@@ -25995,7 +25995,7 @@ as soon as it finds @code{#} unique rows.
In some cases a @code{GROUP BY} can be resolved by reading the key in order
In some cases a @code{GROUP BY} can be resolved by reading the key in order
(or do a sort on the key) and then calculate summaries until the
(or do a sort on the key) and then calculate summaries until the
key value changes. In this case @code{LIMIT #} will not calculate any
key value changes. In this case @code{LIMIT #} will not calculate any
unnecessary @code{GROUP BY}
'
s.
unnecessary @code{GROUP BY}s.
@item
@item
As soon as MySQL has sent the first @code{#} rows to the client, it
As soon as MySQL has sent the first @code{#} rows to the client, it
will abort the query (If you are not using @code{SQL_CALC_FOUND_ROWS}).
will abort the query (If you are not using @code{SQL_CALC_FOUND_ROWS}).
...
@@ -27631,7 +27631,7 @@ that probably will take a very long time. This is useful when an inadvisable
...
@@ -27631,7 +27631,7 @@ that probably will take a very long time. This is useful when an inadvisable
@code{1} (which will allow all @code{SELECT} statements).
@code{1} (which will allow all @code{SELECT} statements).
@item SQL_BUFFER_RESULT = 0 | 1
@item SQL_BUFFER_RESULT = 0 | 1
@code{SQL_BUFFER_RESULT} will force the result from @code{SELECT}
'
s
@code{SQL_BUFFER_RESULT} will force the result from @code{SELECT}s
to be put into a temporary table. This will help MySQL free the
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
table locks early and will help in cases where it takes a long time to
send the result set to the client.
send the result set to the client.
...
@@ -37267,7 +37267,7 @@ automatically depending on the type of columns you are using. The third,
...
@@ -37267,7 +37267,7 @@ automatically depending on the type of columns you are using. The third,
compressed tables, can only be created with the @code{myisampack} tool.
compressed tables, can only be created with the @code{myisampack} tool.
When you @code{CREATE} or @code{ALTER} a table you can for tables that
When you @code{CREATE} or @code{ALTER} a table you can for tables that
doesn't have @code{BLOB}
'
s force the table format to @code{DYNAMIC} or
doesn't have @code{BLOB}s force the table format to @code{DYNAMIC} or
@code{FIXED} with the @code{ROW_FORMAT=#} table option. In the future
@code{FIXED} with the @code{ROW_FORMAT=#} table option. In the future
you will be able to compress/decompress tables by specifying
you will be able to compress/decompress tables by specifying
@code{ROW_FORMAT=compressed | default} to @code{ALTER TABLE}.
@code{ROW_FORMAT=compressed | default} to @code{ALTER TABLE}.
...
@@ -49492,7 +49492,7 @@ Fixed bug that caused duplicated rows when using truncation operator
...
@@ -49492,7 +49492,7 @@ Fixed bug that caused duplicated rows when using truncation operator
@code{*} in boolean full-text search.
@code{*} in boolean full-text search.
@item
@item
Fixed bug in truncation operator of boolean full-text search (wrong results
Fixed bug in truncation operator of boolean full-text search (wrong results
when there are only @code{+word*}
'
s in the query).
when there are only @code{+word*}s in the query).
@item
@item
Fixed bug in boolean full-text search that caused a crash when an identical
Fixed bug in boolean full-text search that caused a crash when an identical
@code{MATCH} expression that did not use an index appeared twice.
@code{MATCH} expression that did not use an index appeared twice.
...
@@ -56463,8 +56463,8 @@ UPDATE table_name SET column=value WHERE unique_key#
...
@@ -56463,8 +56463,8 @@ UPDATE table_name SET column=value WHERE unique_key#
DELETE FROM table_name WHERE unique_key=#
DELETE FROM table_name WHERE unique_key=#
@end example
@end example
@item
@item
@code{SELECT} combined with @code{INSERT} (and very few @code{UPDATE}
'
s
@code{SELECT} combined with @code{INSERT} (and very few @code{UPDATE}s
and @code{DELETE}
'
s.
and @code{DELETE}s.
@item
@item
Many scans / @code{GROUP BY} on the whole table without any writers.
Many scans / @code{GROUP BY} on the whole table without any writers.
@end itemize
@end itemize
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