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
ab5e1ef0
Commit
ab5e1ef0
authored
Jul 24, 2002
by
paul@teton.kitebird.com
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
manual.texi fix typos
parent
69a19525
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
Docs/manual.texi
Docs/manual.texi
+2
-2
No files found.
Docs/manual.texi
View file @
ab5e1ef0
...
...
@@ -8158,7 +8158,7 @@ The following SQL variables have changed name.
@item @code{SQL_MAX_JOIN_SIZE} @tab @code{MAX_JOIN_SIZE}
@item @code{SQL_QUERY_CACHE_TYPE} @tab @code{QUERY_CACHE_TYPE}
@end multitable
The old names still work in MySQL 4.0 but are depr
i
cated.
The old names still work in MySQL 4.0 but are depr
e
cated.
@item
You have to use @code{SET GLOBAL SQL_SLAVE_SKIP_COUNTER=#} instead of
@code{SET SQL_SLAVE_SKIP_COUNTER=#}.
...
...
@@ -14306,7 +14306,7 @@ If you want to restrict the maximum value a startup option can be set to
with @code{SET}, you can define this by using the
@code{--maximum-variable-name} command line option. @xref{SET OPTION}.
Note that when setting a variable to a value, MySQL may automaticly
Note that when setting a variable to a value, MySQL may automatic
al
ly
correct it to stay within a given range and also adjusts the value a
little to fix for the used algorithm.
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