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
25612333
Commit
25612333
authored
Nov 06, 2001
by
arjen@co3064164-a.bitbike.com
Browse files
Options
Browse Files
Download
Plain Diff
Merge arjen@work.mysql.com:/home/bk/mysql-4.0
into co3064164-a.bitbike.com:c:/home/mysql-4.0
parents
d0e83062
eb893a2f
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
148 additions
and
140 deletions
+148
-140
Docs/manual.texi
Docs/manual.texi
+148
-140
No files found.
Docs/manual.texi
View file @
25612333
...
@@ -693,76 +693,85 @@ options to obtain online assistance.
...
@@ -693,76 +693,85 @@ options to obtain online assistance.
@cindex stability
@cindex stability
This section addresses the questions ``How stable is MySQL?'' and
This section addresses the questions ``@emph{How stable is MySQL?}''
``Can I depend on MySQL in this project?'' We will try to clarify
and ``@emph{Can I depend on MySQL in this project?}''
some issues and to answer some of the more important questions that seem to
We will try to clarify these issues and answer some important
concern many people. This section has been put together from information
questions that concern many potential users. The information in this
gathered from the mailing list (which is very active in reporting bugs).
section is based on data gathered from the mailing list, which is
very active in identifying problems as well as reporting types of use.
At TcX, the predecessor of MySQL AB, MySQL has worked without any problems in
projects since mid-1996. Original code stems back from the early 80s,
Original code stems back from the early 80s, providing a stable code
providing a table code base, and the ISAM table format remains backwards
base, and the ISAM table format remains backwards compatible.
compatible. When MySQL was released to a wider public, we noticed that there
At TcX, the predecessor of MySQL AB, MySQL has worked in projects
were some pieces of ``untested code'' that were quickly found by the new users
since mid-1996, without any problems.
who made queries in a manner different than our own. Each new release has had
When MySQL was released to a wider public, we noticed that there were
fewer portability problems than the previous one (even though each has had
some pieces of ``untested code'' that were quickly found by the new
many new features).
users who made different types of queries from us. Each new release
has had fewer portability problems (even though each new release has
Each release of MySQL has been usable, and there have been problems
had many new features).
only when users start to use code from the ``gray zones.'' Naturally, outside
users don't know what the gray zones are; this section attempts to indicate
Each release of MySQL has been usable. There have only been problems
those that are currently known. The descriptions deal with Version 3.23
when users try code from the ``gray zones.'' Naturally, new users
of MySQL. All known and reported bugs are fixed in the latest
don't know what the gray zones are; this section attempts to indicate
version, with the exception of the bugs listed in the bugs section, which
those that are currently known.
are things that are design-related. @xref{Bugs}.
The descriptions mostly deal with Version 3.23 of MySQL.
All known and reported bugs are fixed in the latest version, with the
MySQL is written in multiple layers and different independent modules.
exception of those listed in the bugs section, which are things that
Some of the new modules are listed below with an indication of how
are design-related. @xref{Bugs}.
well-tested each of them is:
MySQL design is multi-layered with independent modules. Some of the
newer modules are listed below with an indication of how well-tested
each of them is:
@cindex modules, list of
@cindex modules, list of
@table @strong
@table @strong
@item Locking --- Gamma
This is very system-dependent. On some systems there are big problems
using standard OS locking (@code{fcntl()}). In these cases, you should run the
MySQL daemon with the @code{--skip-locking} flag. Problems are known
to occur on some Linux systems, and on SunOS when using NFS-mounted file
systems.
@item @strong{MyODBC 2.50} (uses ODBC SDK 2.5) --- Gamma
It seems to work well with some programs.
@item Replication -- Gamma
@item Replication -- Gamma
We are still working on replication, so don't expect this to be rock
Large server clusters using replication are in production use, with
solid yet. On the other hand, some MySQL users are already
good results. Work on enhanced replication features is continuing
using this with good results.
in MySQL 4.0.
@item BDB Tables -- Gamma
@item @code{InnoDB} tables -- Gamma
The Berkeley DB code is very stable, but we are still improving the interface
While the @code{InnoDB} transactional table handler is a fairly recent
between MySQL and BDB tables, so it will take some time before this
addition to @code{MySQL}, it appears to work well and is already being
is tested as well as the other table types.
used in some large, heavy load production systems.
@item InnoDB Tables -- Gamma
@item @code{BDB} tables -- Gamma
This is a recent addition to @code{MySQL}. They appear to work well and
The @code{Berkeley DB} code is very stable, but we are still improving
can be used after some initial testing.
the @code{BDB} transactional table handler interface in MySQL, so it
will take some time before this is as well tested as the other table
@item Automatic recovery of MyISAM tables - Gamma
types.
This only affects the new code that checks if the table was closed properly
on open and executes an automatic check/repair of the table if it wasn't.
@item @code{FULLTEXT} -- Beta
Full text search works but is not yet widely used.
@item FULLTEXT -- Beta
Important enhancements are being implemented for MySQL 4.0.
Text search seems to work, but is still not widely used.
@item @code{MyODBC 2.50} (uses ODBC SDK 2.5) -- Gamma
@item Bulk-insert - Alpha
Increasingly in wide use. Some issues brought up appear to be
application related and independent of the ODBC driver or underlying
database server.
@item Automatic recovery of @code{MyISAM} tables -- Gamma
This status only regards the new code in the @code{MyISAM} table
handler that checks if the table was closed properly on open and
executes an automatic check/repair of the table if it wasn't.
@item Bulk-insert -- Alpha
New feature in MyISAM in MySQL 4.0 for faster insert of many rows.
New feature in MyISAM in MySQL 4.0 for faster insert of many rows.
@item Locking -- Gamma
This is very system-dependent. On some systems there are big problems
using standard OS locking (@code{fcntl()}). In these cases, you should
run @code{mysqld} with the @code{--skip-locking} flag.
Problems are known to occur on some Linux systems, and on SunOS when
using NFS-mounted file systems.
@end table
@end table
MySQL AB provides high-quality support for paying customers, but the
MySQL AB provides high-quality support for paying customers, but the
MySQL mailing list usually provides answers to common questions.
MySQL mailing list usually provides answers to common questions.
Bugs are usually fixed right away with a patch; for serious bugs,
there is
Bugs are usually fixed right away with a patch; for serious bugs,
almost always a new release.
there is
almost always a new release.
@node Table size, Year 2000 compliance, Stability, What-is
@node Table size, Year 2000 compliance, Stability, What-is
...
@@ -28955,7 +28964,7 @@ A few are reserved because MySQL needs them and is
...
@@ -28955,7 +28964,7 @@ A few are reserved because MySQL needs them and is
@c START_OF_RESERVED_WORDS
@c START_OF_RESERVED_WORDS
@multitable @columnfractions .25 .25 .25 .25
@multitable @columnfractions .25 .25 .25 .25
@c Reserved word list updated T
hu Oct 18 21:44:01 2001 by jcole
.
@c Reserved word list updated T
ue Nov 6 08:50:27 2001 by arjen
.
@c To regenerate, use Support/update-reserved-words.pl.
@c To regenerate, use Support/update-reserved-words.pl.
@item @code{ADD} @tab @code{ALL}
@item @code{ADD} @tab @code{ALL}
...
@@ -28963,86 +28972,85 @@ A few are reserved because MySQL needs them and is
...
@@ -28963,86 +28972,85 @@ A few are reserved because MySQL needs them and is
@item @code{AND} @tab @code{AS}
@item @code{AND} @tab @code{AS}
@tab @code{ASC} @tab @code{BETWEEN}
@tab @code{ASC} @tab @code{BETWEEN}
@item @code{BIGINT} @tab @code{BINARY}
@item @code{BIGINT} @tab @code{BINARY}
@tab @code{BINLOG} @tab @code{BLOB}
@tab @code{BLOB} @tab @code{BOTH}
@item @code{BOTH} @tab @code{BY}
@item @code{BY} @tab @code{CASCADE}
@tab @code{CASCADE} @tab @code{CASE}
@tab @code{CASE} @tab @code{CHANGE}
@item @code{CHANGE} @tab @code{CHARACTER}
@item @code{CHARACTER} @tab @code{COLUMN}
@tab @code{COLUMN} @tab @code{CONSTRAINT}
@tab @code{CONSTRAINT} @tab @code{CREATE}
@item @code{CREATE} @tab @code{CROSS}
@item @code{CROSS} @tab @code{CURRENT_DATE}
@tab @code{CURRENT_DATE} @tab @code{CURRENT_TIME}
@tab @code{CURRENT_TIME} @tab @code{CURRENT_TIMESTAMP}
@item @code{CURRENT_TIMESTAMP} @tab @code{DATABASE}
@item @code{DATABASE} @tab @code{DATABASES}
@tab @code{DATABASES} @tab @code{DAY_HOUR}
@tab @code{DAY_HOUR} @tab @code{DAY_MINUTE}
@item @code{DAY_MINUTE} @tab @code{DAY_SECOND}
@item @code{DAY_SECOND} @tab @code{DECIMAL}
@tab @code{DECIMAL} @tab @code{DEFAULT}
@tab @code{DEFAULT} @tab @code{DELAYED}
@item @code{DELAYED} @tab @code{DELETE}
@item @code{DELETE} @tab @code{DESC}
@tab @code{DESC} @tab @code{DISTINCTROW}
@tab @code{DISTINCTROW} @tab @code{DOUBLE}
@item @code{DOUBLE} @tab @code{DROP}
@item @code{DROP} @tab @code{ELSE}
@tab @code{ELSE} @tab @code{ENCLOSED}
@tab @code{ENCLOSED} @tab @code{ESCAPED}
@item @code{ESCAPED} @tab @code{EVENTS}
@item @code{EXISTS} @tab @code{EXPLAIN}
@tab @code{EXISTS} @tab @code{EXPLAIN}
@tab @code{FIELDS} @tab @code{FLOAT}
@item @code{FIELDS} @tab @code{FLOAT}
@item @code{FOR} @tab @code{FOREIGN}
@tab @code{FOR} @tab @code{FOREIGN}
@tab @code{FROM} @tab @code{FULLTEXT}
@item @code{FROM} @tab @code{FULLTEXT}
@item @code{GRANT} @tab @code{GROUP}
@tab @code{GRANT} @tab @code{GROUP}
@tab @code{HAVING} @tab @code{HIGH_PRIORITY}
@item @code{HAVING} @tab @code{HIGH_PRIORITY}
@item @code{HOUR_MINUTE} @tab @code{HOUR_SECOND}
@tab @code{HOUR_MINUTE} @tab @code{HOUR_SECOND}
@tab @code{IF} @tab @code{IGNORE}
@item @code{IF} @tab @code{IGNORE}
@item @code{IN} @tab @code{INDEX}
@tab @code{IN} @tab @code{INDEX}
@tab @code{INFILE} @tab @code{INNER}
@item @code{INFILE} @tab @code{INNER}
@item @code{INSERT} @tab @code{INSERT_ID}
@tab @code{INSERT} @tab @code{INSERT_ID}
@tab @code{INTEGER} @tab @code{INTERVAL}
@item @code{INTEGER} @tab @code{INTERVAL}
@item @code{INTO} @tab @code{IS}
@tab @code{INTO} @tab @code{IS}
@tab @code{JOIN} @tab @code{KEY}
@item @code{JOIN} @tab @code{KEY}
@item @code{KEYS} @tab @code{KILL}
@tab @code{KEYS} @tab @code{KILL}
@tab @code{LAST_INSERT_ID} @tab @code{LEADING}
@item @code{LAST_INSERT_ID} @tab @code{LEADING}
@item @code{LEFT} @tab @code{LIKE}
@tab @code{LEFT} @tab @code{LIKE}
@tab @code{LIMIT} @tab @code{LINES}
@item @code{LIMIT} @tab @code{LINES}
@item @code{LOAD} @tab @code{LOCK}
@tab @code{LOAD} @tab @code{LOCK}
@tab @code{LONG} @tab @code{LONGBLOB}
@item @code{LONG} @tab @code{LONGBLOB}
@item @code{LONGTEXT} @tab @code{LOW_PRIORITY}
@tab @code{LONGTEXT} @tab @code{LOW_PRIORITY}
@tab @code{MASTER_LOG_SEQ} @tab @code{MASTER_SERVER_ID}
@item @code{MASTER_LOG_SEQ} @tab @code{MASTER_SERVER_ID}
@item @code{MATCH} @tab @code{MEDIUMBLOB}
@tab @code{MATCH} @tab @code{MEDIUMBLOB}
@tab @code{MEDIUMTEXT} @tab @code{MIDDLEINT}
@item @code{MEDIUMTEXT} @tab @code{MIDDLEINT}
@item @code{MINUTE_SECOND} @tab @code{NATURAL}
@tab @code{MINUTE_SECOND} @tab @code{NATURAL}
@tab @code{NOT} @tab @code{NULL}
@item @code{NOT} @tab @code{NULL}
@item @code{NUMERIC} @tab @code{ON}
@tab @code{NUMERIC} @tab @code{ON}
@tab @code{OPTIMIZE} @tab @code{OPTION}
@item @code{OPTIMIZE} @tab @code{OPTION}
@item @code{OPTIONALLY} @tab @code{OR}
@tab @code{OPTIONALLY} @tab @code{OR}
@tab @code{ORDER} @tab @code{OUTER}
@item @code{ORDER} @tab @code{OUTER}
@item @code{OUTFILE} @tab @code{PARTIAL}
@tab @code{OUTFILE} @tab @code{PARTIAL}
@tab @code{PRECISION} @tab @code{PRIMARY}
@item @code{PRECISION} @tab @code{PRIMARY}
@item @code{PRIVILEGES} @tab @code{PROCEDURE}
@tab @code{PRIVILEGES} @tab @code{PROCEDURE}
@tab @code{PURGE} @tab @code{READ}
@item @code{PURGE} @tab @code{READ}
@item @code{REAL} @tab @code{REFERENCES}
@tab @code{REAL} @tab @code{REFERENCES}
@tab @code{RENAME} @tab @code{REPLACE}
@item @code{RENAME} @tab @code{REPLACE}
@item @code{REQUIRE} @tab @code{RESTRICT}
@tab @code{REQUIRE} @tab @code{RESTRICT}
@tab @code{RETURNS} @tab @code{REVOKE}
@item @code{RETURNS} @tab @code{REVOKE}
@item @code{RIGHT} @tab @code{RLIKE}
@tab @code{RIGHT} @tab @code{RLIKE}
@tab @code{SELECT} @tab @code{SET}
@item @code{SELECT} @tab @code{SET}
@item @code{SHOW} @tab @code{SMALLINT}
@tab @code{SHOW} @tab @code{SMALLINT}
@tab @code{SONAME} @tab @code{SQL_AUTO_IS_NULL}
@item @code{SONAME} @tab @code{SQL_AUTO_IS_NULL}
@item @code{SQL_BIG_RESULT} @tab @code{SQL_BIG_SELECTS}
@tab @code{SQL_BIG_RESULT} @tab @code{SQL_BIG_SELECTS}
@tab @code{SQL_BIG_TABLES} @tab @code{SQL_BUFFER_RESULT}
@item @code{SQL_BIG_TABLES} @tab @code{SQL_BUFFER_RESULT}
@item @code{SQL_CALC_FOUND_ROWS} @tab @code{SQL_LOG_BIN}
@tab @code{SQL_CALC_FOUND_ROWS} @tab @code{SQL_LOG_BIN}
@tab @code{SQL_LOG_OFF} @tab @code{SQL_LOG_UPDATE}
@item @code{SQL_LOG_OFF} @tab @code{SQL_LOG_UPDATE}
@item @code{SQL_LOW_PRIORITY_UPDATES} @tab @code{SQL_SAFE_UPDATES}
@tab @code{SQL_LOW_PRIORITY_UPDATES} @tab @code{SQL_SAFE_UPDATES}
@tab @code{SQL_SELECT_LIMIT} @tab @code{SQL_SLAVE_SKIP_COUNTER}
@item @code{SQL_SELECT_LIMIT} @tab @code{SQL_SLAVE_SKIP_COUNTER}
@item @code{SQL_SMALL_RESULT} @tab @code{SQL_WARNINGS}
@tab @code{SQL_SMALL_RESULT} @tab @code{SQL_WARNINGS}
@tab @code{SSL} @tab @code{STARTING}
@item @code{SSL} @tab @code{STARTING}
@item @code{STRAIGHT_JOIN} @tab @code{TABLE}
@tab @code{STRAIGHT_JOIN} @tab @code{TABLE}
@tab @code{TABLES} @tab @code{TERMINATED}
@item @code{TABLES} @tab @code{TERMINATED}
@item @code{THEN} @tab @code{TINYBLOB}
@tab @code{THEN} @tab @code{TINYBLOB}
@tab @code{TINYINT} @tab @code{TINYTEXT}
@item @code{TINYINT} @tab @code{TINYTEXT}
@item @code{TO} @tab @code{TRAILING}
@tab @code{TO} @tab @code{TRAILING}
@tab @code{UNION} @tab @code{UNIQUE}
@item @code{UNION} @tab @code{UNIQUE}
@item @code{UNLOCK} @tab @code{UNSIGNED}
@tab @code{UNLOCK} @tab @code{UNSIGNED}
@tab @code{UPDATE} @tab @code{USAGE}
@item @code{UPDATE} @tab @code{USAGE}
@item @code{USE} @tab @code{USING}
@tab @code{USE} @tab @code{USING}
@tab @code{VALUES} @tab @code{VARBINARY}
@item @code{VALUES} @tab @code{VARBINARY}
@item @code{VARCHAR} @tab @code{VARYING}
@tab @code{VARCHAR} @tab @code{VARYING}
@tab @code{WHEN} @tab @code{WHERE}
@item @code{WHEN} @tab @code{WHERE}
@item @code{WITH} @tab @code{WRITE}
@tab @code{WITH} @tab @code{WRITE}
@tab @code{YEAR_MONTH} @tab @code{ZEROFILL}
@item @code{YEAR_MONTH} @tab @code{ZEROFILL}
@end multitable
@end multitable
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