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
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
nexedi
MariaDB
Commits
a891a64e
Commit
a891a64e
authored
Feb 02, 2002
by
unknown
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
manual.texi fix typos pointed out by mailing list reader
Docs/manual.texi: typos pointed out by mailing list reader
parent
c0c357bd
Changes
1
Show 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 @
a891a64e
...
@@ -3706,7 +3706,7 @@ this without sacrifying the speed or compromise the code.
...
@@ -3706,7 +3706,7 @@ this without sacrifying the speed or compromise the code.
@node TODO MySQL 4.0, TODO MySQL 4.1, TODO, TODO
@node TODO MySQL 4.0, TODO MySQL 4.1, TODO, TODO
@subsection Things That Should be in 4.0
@subsection Things That Should be in 4.0
We
have now
in the final stages one the development of the MySQL Server
We
are
in the final stages one the development of the MySQL Server
4.0. server. The target is to quickly implement the rest of the
4.0. server. The target is to quickly implement the rest of the
following features and then shift development to MySQL Server
following features and then shift development to MySQL Server
4.1. @xref{MySQL 4.0 In A Nutshell}.
4.1. @xref{MySQL 4.0 In A Nutshell}.
...
@@ -3791,7 +3791,7 @@ characters in database, table and column names.
...
@@ -3791,7 +3791,7 @@ characters in database, table and column names.
Add @code{record_in_range()} method to @code{MERGE} tables to be
Add @code{record_in_range()} method to @code{MERGE} tables to be
able to choose the right index when there is many to choose from. We should
able to choose the right index when there is many to choose from. We should
also extend the info interface to get the key distribution for each index,
also extend the info interface to get the key distribution for each index,
o
f @code{analyze} is run on all sub tables.
i
f @code{analyze} is run on all sub tables.
@item
@item
@code{RENAME TABLE} on a table used in an active @code{MERGE} table may
@code{RENAME TABLE} on a table used in an active @code{MERGE} table may
corrupt the table.
corrupt the table.
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