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
d3ab09af
Commit
d3ab09af
authored
Mar 08, 2002
by
unknown
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Processed docs@ feedback about typos in manual.
parent
95d01af6
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
7 deletions
+7
-7
Docs/manual.texi
Docs/manual.texi
+7
-7
No files found.
Docs/manual.texi
View file @
d3ab09af
...
...
@@ -27509,8 +27509,8 @@ You might want to do this, for example, to move a database to a file
system with more free space or increase the speed of your system by
spreading your tables to different disk.
The recommended
may to do this, is to just symlink databases to different
disk and only symlink tables as a last resort.
The recommended
way to do this, is to just symlink databases to a
di
fferent di
sk and only symlink tables as a last resort.
@cindex databases, symbolic links
@menu
...
...
@@ -27577,11 +27577,11 @@ files. This happens because the above command works by creating a
temporary file in the database directory and when the command is
complete, replace the original file with the temporary file.
You should not symlink tables on system
that does
n't have a fully
You should not symlink tables on system
s that do
n't have a fully
working @code{realpath()} call. (At least Linux and Solaris support
@code{realpath()})
In MySQL 4.0 symlinks
is
only fully supported for @code{MyISAM}
In MySQL 4.0 symlinks
are
only fully supported for @code{MyISAM}
tables. For other table types you will probably get strange problems
when doing any of the above mentioned commands.
...
...
@@ -32484,7 +32484,7 @@ Encrypts the string with the given key using the DES algorithm, which
provides strong encryption.
Note that this function only works if you have configured MySQL with
S
L
L support. @xref{Secure connections}.
S
S
L support. @xref{Secure connections}.
The encryption key to use is chosen the following way:
...
...
@@ -32540,7 +32540,7 @@ crypted_credit_card = DES_ENCRYPT("credit_card_number");
Decrypts a string crypted with @code{des_encrypt()}.
Note that this function only works if you have configured MySQL with
S
L
L support. @xref{Secure connections}.
S
S
L support. @xref{Secure connections}.
If one only gives this a string argument, then it will use the right key
from the @code{des-key-file} to decrypt the message. For this to work
...
...
@@ -48649,7 +48649,7 @@ Contributed to Development on Linux/Alpha.
@item SWSoft
Development on the embedded @code{mysqld} version.
@item FutureQuest
@code{--skip-show-
variables
}
@code{--skip-show-
database
}
@end 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