This is the MySQL reference manual; it documents MySQL version 3.23.9-alpha.
MySQL is a very fast, multi-threaded, multi-user and robust SQL (Structured Query Language) database server.
For Unix and OS/2 platforms, MySQL is basically free; for Microsoft platforms you must get a MySQL license after a trial time of 30 days. See section 3 MySQL licensing and support.
The MySQL home page provides the latest information about MySQL.
For a discussion of MySQL's capabilities, see section 1.5 The main features of MySQL.
For installation instructions, see section 4 Installing MySQL. For tips on porting MySQL to new machines or operating systems, see section G Comments on porting to other systems.
For information about upgrading from a 3.21 release, see section 4.16.2 Upgrading from a 3.21 version to 3.22.
For a tutorial introduction to MySQL, see section 8 MySQL Tutorial.
For examples of SQL and benchmarking information, see the benchmarking directory (`sql-bench' in the distribution).
For a history of new features and bug fixes, see section D MySQL change history.
For a list of currently known bugs and misfeatures, see section E Known errors and design deficiencies in MySQL.
For future plans, see section F List of things we want to add to MySQL in the future (The TODO).
For a list of all the contributors to this project, see section C Contributors to MySQL.
IMPORTANT:
Send error (often called bugs) reports, questions and comments to the mailing list at mysql@lists.mysql.com. See section 2.3 How to report bugs or problems.
For source distributions, the mysqlbug script can be found in the
`scripts' directory. For binary distributions, mysqlbug can
be found in the `bin' directory.
If you have any suggestions concerning additions or corrections to this manual, please send them to the manual team at (docs@mysql.com).
MySQL is a true multi-user, multi-threaded SQL database
server. SQL (Structured Query Language) is the most popular and
standardized database language in the world. MySQL is a
client/server implementation that consists of a server daemon
mysqld and many different client programs and libraries.
SQL is a standardized language that makes it easy to store, update and access information. For example, you can use SQL to retrieve product information and store customer information for a web site. MySQL is also fast and flexible enough to allow you to store logs and pictures in it.
The main goals of MySQL are speed, robustness and ease of use. MySQL was originally developed because we needed a SQL server that could handle very large databases an order of magnitude faster than what any database vendor could offer to us on inexpensive hardware. We have now been using MySQL since 1996 in an environment with more than 40 databases containing 10,000 tables, of which more than 500 have more than 7 million rows. This is about 100 gigabytes of mission-critical data.
The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. Although MySQL is still under development, it already offers a rich and highly useful function set.
The official way to pronounce MySQL is ``My Ess Que Ell'' (Not MY-SEQUEL).
This manual is currently available in Texinfo, plain text, Info, HTML, PostScript and PDF versions. Because of their size, PostScript and PDF versions are not included with the main MySQL distribution, but are available for separate download at http://www.mysql.com.
The primary document is the Texinfo file. The HTML version is produced
automatically with a modified version of texi2html. The plain
text and Info versions are produced with makeinfo. The Postscript
version is produced using texi2dvi and dvips. The PDF
version is produced with pdftex.
This manual is written and maintained by David Axmark, Michael (Monty) Widenius and Paul DuBois. For other contributors, see section C Contributors to MySQL.
This manual uses certain typographical conventions:
constant
mysqladmin works, invoke it with the
--help option.''
When commands are shown that are meant to be executed by a particular
program, the program is indicated by the prompt shown with the command. For
example, shell> indicates a command that you execute from your login
shell, and mysql> indicates a command that you execute from the
mysql client:
shell> type a shell command here mysql> type a mysql command here
Shell commands are shown using Bourne shell syntax. If you are using a
csh-style shell, you may need to issue commands slightly differently.
For example, the sequence to set an environment variable and run a command
looks like this in Bourne shell syntax:
shell> VARNAME=value some_command
For csh, you would execute the sequence like this:
shell> setenv VARNAME value shell> some_command
Database, table and column names often must be substituted into commands. To
indicate that such substitution is necessary, this manual uses
db_name, tbl_name and col_name. For example, you might
see a statement like this:
mysql> SELECT col_name FROM db_name.tbl_name;
This means that if you were to enter a similar statement, you would supply your own database, table and column names, perhaps like this:
mysql> SELECT author_name FROM biblio_db.author_list;
SQL statements may be written in uppercase or lowercase. When this manual
shows a SQL statement, uppercase is used for particular keywords if those
keywords are under discussion (to emphasize them) and lowercase is used for
the rest of the statement. So you might see the following in a discussion of
the SELECT statement:
mysql> SELECT count(*) FROM tbl_name;
On the other hand, in a discussion of the COUNT() function, the
statement would be written like this:
mysql> select COUNT(*) from tbl_name;
If no particular emphasis is intended, all keywords are written uniformly in uppercase.
In syntax descriptions, square brackets (`[' and `]') are used to indicate optional words or clauses:
DROP TABLE [IF EXISTS] tbl_name
When a syntax element consists of a number of alternatives, the alternatives are separated by vertical bars (`|'). When one member from a set of choices may be chosen, the alternatives are listed within square brackets. When one member from a set of choices must be chosen, the alternatives are listed within braces (`{' and `}'):
TRIM([[BOTH | LEADING | TRAILING] [remstr] FROM] str)
{DESCRIBE | DESC} tbl_name {col_name | wild}
We once started off with the intention of using mSQL to connect to our
tables using our own fast low-level (ISAM) routines. However, after some
testing we came to the conclusion that mSQL was not fast enough or
flexible enough for our needs. This resulted in a new SQL interface to our
database but with almost the same API interface as mSQL. This API was
chosen to ease porting of third-party code.
The derivation of the name MySQL is not perfectly clear. Our base directory and a large number of our libraries and tools have had the prefix ``my'' for well over 10 years. However, Monty's daughter (some years younger) is also named My. So which of the two gave its name to MySQL is still a mystery, even for us.
While this manual is still the right place for up to date techical information, its primary goal is to contain everything there is to know about MySQL. And it is sometimes nice to have a bound book to read in bed or while you travel. Here are a list of books about MySQL (in English).
| Title | MySQL |
| Publisher | New Riders |
| Author | Paul DuBois |
| Pub Date | 1st Edition December 1999 |
| ISBN | 0735709211 |
| Pages | 800 |
| Price | $49.99 US |
| Downloadable examples | samp_db.tar.gz |
Foreword by Michael "Monty" Widenius, MySQL Moderator
In MySQL, Paul DuBois provides you with a comprehensive guide to one of the most popular relational database systems. Paul has contributed to the online documentation for MySQL, and is an active member of the MySQL community. The principal MySQL developer, Monty Widenius, and a network of his fellow developers reviewed the manuscript, providing Paul with the kind of insight no one else could supply.
Instead of merely giving you a general overview of MySQL, Paul teaches you how to make the most of its capabilities. Through two sample database applications that run throughout the book, he gives you solutions to problems you're sure to face. He helps you integrate MySQL efficiently with third-party tools, such as PHP and Perl, enabling you to generate dynamic Web pages through database queries. He teaches you to write programs that access MySQL databases, and also provides a comprehensive set of references to column types, operators, functions, SQL syntax, MySQL programming, C API, Perl DBI, and PHP API. MySQL simply gives you the kind of information you won't find anywhere else.
If you use MySQL, this book provides you with:
| Title | MySQL & mSQL |
| Publisher | O'Reilly |
| Authors | Randy Jay Yarger, George Reese & Tim King |
| Pub Date | 1st Edition July 1999 |
| ISBN | 1-56592-434-7, Order Number: 4347 |
| Pages | 506 |
| Price | $34.95 |
This book teaches you how to use MySQL and mSQL, two popular and robust database products that support key subsets of SQL on both Linux and UNIX systems. Anyone who knows basic C, Java, Perl, or Python can write a program to interact with a database, either as a stand-alone application or through a Web page. This book takes you through the whole process, from installation and configuration to programming interfaces and basic administration. Includes ample tutorial material.
The following list describes some of the important characteristics of MySQL:
FLOAT, DOUBLE, CHAR, VARCHAR,
TEXT, BLOB, DATE, TIME, DATETIME,
TIMESTAMP, YEAR, SET and ENUM types. See section 7.3 Column types.
SELECT and WHERE
parts of queries. Example:
mysql> SELECT CONCAT(first_name, " ", last_name) FROM tbl_name
WHERE income/dependents > 10000 AND age > 30;
GROUP BY and ORDER BY
clauses. Support for group functions (COUNT(),
COUNT(DISTINCT), AVG(), STD(), SUM(),
MAX() and MIN()).
LEFT OUTER JOIN with ANSI SQL and ODBC syntax.
CHAR or VARCHAR field.
INSERT to insert a
subset of a table's columns; those columns that are not explicitly given
values are set to their default values.
libtool for portability.
purify).
myisamchk, a very fast utility for table checking, optimization
and repair.
See section 13 Maintaining a MySQL installation.
DELETE, INSERT, REPLACE, and UPDATE return
how many rows were changed (affected).
ABS
is a valid column name. The only restriction is that for a function call, no
spaces are allowed between the function name and the `(' that follows it.
See section 7.31 Is MySQL picky about reserved words?.
--help or -?
options to obtain online assistance.
SHOW command can be used to retrieve
information about databases, tables and indexes. The EXPLAIN command
can be used to determine how the optimizer resolves a query.
This section addresses the questions, ``how stable is MySQL?'' and, ``can I depend on MySQL in this project?'' Here we will try to clarify some issues and to answer some of the more important questions that seem to concern many people. This section has been put together from information gathered from the mailing list (which is very active in reporting bugs).
At TcX, MySQL has worked without any problems in our projects since mid-1996. When MySQL was released to a wider public, we noticed that there were some pieces of ``untested code'' that were quickly found by the new users who made queries in a manner different than our own. Each new release has had fewer portability problems than the previous one (even though each has had many new features), and we hope that it will be possible to label one of the next releases ``stable''.
Each release of MySQL has been usable and there have been problems only when users start to use code from ``the gray zones''. Naturally, outside users can't know what the gray zones are; this section attempts to indicate those that are currently known. The descriptions deal with the 3.22.x version of MySQL. All known and reported bugs are fixed in the latest version, with the exception of the bugs listed in the bugs section, which are things that are ``design''-related. See section E Known errors and design deficiencies in MySQL.
MySQL is written in multiple layers and different independent modules. These modules are listed below with an indication of how well-tested each of them is:
mysql, mysqladmin and mysqlshow,
mysqldump, and mysqlimport.
fcntl()). In these cases, you should run the
MySQL daemon with the --skip-locking flag. Problems are known
to occur on some Linux systems and on SunOS when using NFS-mounted file
systems.
fcntl() call, which is fixed
by using the --skip-locking option to mysqld. Some people
have reported lockup problems with the 0.5 release.
SELECT
statements are usually done in one time frame so there shouldn't be a mutex
locking/thread juggling.
LOAD DATA ..., INSERT ... SELECT -- Stable
ALTER TABLE -- Stable
mysqlaccess -- Stable
GRANT -- Gamma
TcX provides email support for paying customers, but the MySQL mailing list usually provides answers to common questions. Bugs are usually fixed right away with a patch; for serious bugs, there is almost always a new release.
MySQL itself has no problems with Year 2000 (Y2K) compliance:
2069; all 2-digit years are regarded to be in the range
1970 to 2069, which means that if you store 01 in a
year column, MySQL treats it as 2001.
YEAR column type
can store years 0 and 1901 to 2155 in 1 byte and display
them using 2 or 4 digits.
You may run into problems with applications that use MySQL in a
way that is not Y2K-safe. For example, many old applications store
or manipulate years using 2-digit values (which are ambiguous) rather than
4-digit values. This problem may be compounded by applications that use
values such as 00 or 99 as ``missing'' value indicators.
Unfortunately, these problems may be difficult to fix, since different applications may be written by different programmers, each of whom may use a different set of conventions and date-handling functions.
Here is a simple demonstration illustrating that MySQL doesn't have any problems with dates until the year 2030!
mysql> DROP TABLE IF EXISTS y2k;
mysql> CREATE TABLE y2k (date date, date_time datetime, time_stamp timestamp);
mysql> INSERT INTO y2k VALUES ("1998-12-31","1998-12-31 23:59:59",19981231235959);
mysql> INSERT INTO y2k VALUES ("1999-01-01","1999-01-01 00:00:00",19990101000000);
mysql> INSERT INTO y2k VALUES ("1999-09-09","1999-09-09 23:59:59",19990909235959);
mysql> INSERT INTO y2k VALUES ("2000-01-01","2000-01-01 00:00:00",20000101000000);
mysql> INSERT INTO y2k VALUES ("2000-02-28","2000-02-28 00:00:00",20000228000000);
mysql> INSERT INTO y2k VALUES ("2000-02-29","2000-02-29 00:00:00",20000229000000);
mysql> INSERT INTO y2k VALUES ("2000-03-01","2000-03-01 00:00:00",20000301000000);
mysql> INSERT INTO y2k VALUES ("2000-12-31","2000-12-31 23:59:59",20001231235959);
mysql> INSERT INTO y2k VALUES ("2001-01-01","2001-01-01 00:00:00",20010101000000);
mysql> INSERT INTO y2k VALUES ("2004-12-31","2004-12-31 23:59:59",20041231235959);
mysql> INSERT INTO y2k VALUES ("2005-01-01","2005-01-01 00:00:00",20050101000000);
mysql> INSERT INTO y2k VALUES ("2030-01-01","2030-01-01 00:00:00",20300101000000);
mysql> INSERT INTO y2k VALUES ("2050-01-01","2050-01-01 00:00:00",20500101000000);
mysql> SELECT * FROM y2k;
+------------+---------------------+----------------+
| date | date_time | time_stamp |
+------------+---------------------+----------------+
| 1998-12-31 | 1998-12-31 23:59:59 | 19981231235959 |
| 1999-01-01 | 1999-01-01 00:00:00 | 19990101000000 |
| 1999-09-09 | 1999-09-09 23:59:59 | 19990909235959 |
| 2000-01-01 | 2000-01-01 00:00:00 | 20000101000000 |
| 2000-02-28 | 2000-02-28 00:00:00 | 20000228000000 |
| 2000-02-29 | 2000-02-29 00:00:00 | 20000229000000 |
| 2000-03-01 | 2000-03-01 00:00:00 | 20000301000000 |
| 2000-12-31 | 2000-12-31 23:59:59 | 20001231235959 |
| 2001-01-01 | 2001-01-01 00:00:00 | 20010101000000 |
| 2004-12-31 | 2004-12-31 23:59:59 | 20041231235959 |
| 2005-01-01 | 2005-01-01 00:00:00 | 20050101000000 |
| 2030-01-01 | 2030-01-01 00:00:00 | 20300101000000 |
| 2050-01-01 | 2050-01-01 00:00:00 | 00000000000000 |
+------------+---------------------+----------------+
13 rows in set (0.00 sec)
This shows that the DATE and DATETIME types are will not
give any problems with future dates (they handle dates until the year
9999).
The TIMESTAMP type, that is used to store the current time, has a
range up to only 2030-01-01. TIMESTAMP has a range of
1970 to 2030 on 32-bit machines (signed value). On 64-bit
machines it handles times up to 2106 (unsigned value).
Even though MySQL is Y2K-compliant, it is your responsibility to provide unambiguous input. See section 7.3.6.1 Y2K issues and date types for MySQL's rules for dealing with ambiguous date input data (data containing 2-digit year values).
This book has been recommended by a several people on the MySQL mailing list:
Judith S. Bowman, Sandra L. Emerson and Marcy Darnovsky The Practical SQL Handbook: Using Structured Query Language Second Edition Addison-Wesley ISBN 0-201-62623-3 http://www.awl.com
This book has also received some recommendations by MySQL users:
Martin Gruber Understanding SQL ISBN 0-89588-644-8 Publisher Sybex 510 523 8233 Alameda, CA USA
A SQL tutorial is available on the net at http://www.geocities.com/SiliconValley/Vista/2207/sql1.html
SQL in 21 Tagen (online book in German language): http://www.mut.de/leseecke/buecher/sql/inhalt.htm
MySQL with other programsmSQL
mSQL TCL
DBI/DBD.
DBI/DBD modules homepage
There are also many web pages that use MySQL. See section A Some MySQL users. Send any additions to this list to MySQL logo somewhere (It is okay to have it on a ``used tools'' page or something similar) to be added.
To subscribe to the main MySQL mailing list, send a message to the electronic mail address mysql-subscribe@lists.mysql.com.
To unsubscribe from the main MySQL mailing list, send a message to the electronic mail address mysql-unsubscribe@lists.mysql.com.
Only the address to which you send your messages is significant. The subject line and the body of the message are ignored.
If your reply address is not valid, you can specify your address explicitly.
Adding a hyphen to the subscribe or unsubscribe command word, followed by
your address with the `@' character in your address replaced by a
`='. For example, to subscribe john@host.domain, send a message
to mysql-subscribe-john=host.domain@lists.mysql.com.
Mail to mysql-subscribe@lists.mysql.com or ezmlm mailing list processor. Information about ezmlm is available at the ezmlm Website.
To post a message to the list itself, send your message to
mysql@lists.mysql.com. However, please do not send mail about
subscribing or unsubscribing to mysql@lists.mysql.com, since any
mail sent to that address is distributed automatically to thousands of other
users.
Your local site may have many subscribers to mysql@lists.mysql.com.
If so, it may have a local mailing list, so that messages sent from
lists.mysql.com to your site are propagated to the local list. In such
cases, please contact your system administrator to be added to or dropped
from the local MySQL list.
The following MySQL mailing lists exist:
announce
mysql
mysql-digest
mysql list in digest form. That means you get all individual
messages, sent as one large mail message once a day.
java
java-digest
java list.
win32
win32-digest
win32 list.
myodbc
myodbc-digest
myodbc list.
msql-mysql-modules
msql-mysql-modules-digest
msql-mysql-modules list.
developer
developer-digest
developer list.
You subscribe or unsubscribe to all lists in the same way as described
above. In your subscribe or unsubscribe message, just put the appropriate
mailing list name rather than mysql. For example, to subscribe to or
unsubscribe from the myodbc list, send a message to
Before posting a bug report or question, please do the following:
http://www.mysql.com/Manual_chapter/manual_toc.htmlWe try to keep the manual up to date by updating it frequently with solutions to newly found problems!
http://www.mysql.com/doc.html
If you can't find an answer in the manual or the archives, check with your local MySQL expert. If you still can't find an answer to your question, go ahead and read the next section about how to send mail to
Writing a good bug report takes patience, but doing it right the first time saves time for us and for you. This section will help you write your report correctly so that you don't waste your time doing things that may not help us much or at all.
We encourage everyone to use the mysqlbug script to generate a bug
report (or a report about any problem), if possible. mysqlbug can be
found in the `scripts' directory in the source distribution, or, for a
binary distribution, in the `bin' directory under your MySQL
installation directory. If you are unable to use mysqlbug, you should
still include all the necessary information listed in this section.
The mysqlbug script helps you generate a report by determining much
of the following information automatically, but if something important is
missing, please include it with your message! Please read this section
carefully and make sure that all the information described here is included
in your report.
Remember that it is possible to respond to a message containing too much information, but not to one containing too little. Often people omit facts because they think they know the cause of a problem and assume that some details don't matter. A good principle is: if you are in doubt about stating something, state it! It is a thousand times faster and less troublesome to write a couple of lines more in your report than to be forced to ask again and wait for the answer because you didn't include enough information the first time.
The most common errors are that people don't indicate the version number of the MySQL distribution they are using, or don't indicate what platform they have MySQL installed on (including the platform version number). This is highly relevant information and in 99 cases out of 100 the bug report is useless without it! Very often we get questions like ``Why doesn't this work for me?'' and then we find that the feature requested wasn't implemented in that MySQL version, or that a bug described in a report has been fixed already in newer MySQL versions. Sometimes the error is platform dependent; in such cases, it is next to impossible to fix anything without knowing the operating system and the version number of the platform.
Remember also to provide information about your compiler, if it is related to the problem. Often people find bugs in compilers and think the problem is MySQL related. Most compilers are under development all the time and become better version by version, too. To determine whether or not your problem depends on your compiler, we need to know what compiler is used. Note that every compiling problem should be regarded as a bug report and reported accordingly.
It is most helpful when a good description of the problem is included in the bug report. That is, a good example of all the things you did that led to the problem and the problem itself exactly described. The best reports are those that include a full example showing how to reproduce the bug or problem.
If a program produces an error message, it is very important to include the message in your report! If we try to search for something from the archives using programs, it is better that the error message reported exactly matches the one that the program produces. (Even the case sensitivity should be observed!) You should never try to remember what the error message was; instead, copy and paste the entire message into your report!
If you have a problem with MyODBC, you should try to genereate a MyODBC trace file. See section 16.6 Reporting problems with MyODBC.
Please remember that many of the people who will read your report will
do so using an 80-column display. When generating reports or examples
using the mysql command line tool, you should therefore use
the --vertical option (or the \G statement terminator)
for output which would exceed the available width for such a display
(for example, with the EXPLAIN SELECT statement; see the
example below).
Please include the following information in your report:
mysqladmin version. mysqladmin can be
found in the `bin' directory under your MySQL installation
directory.
uname -a.
mysqldump --no-data db_name tbl_name1 tbl_name2 ... This is very easy
to do and is a powerful way to get information about any table in a database
that will help us create a situation matching the one you have.
SELECT statements, you should
always include the output of EXPLAIN SELECT ..., and at least the
number of rows that the SELECT statement produces. The more
information you give about your situation, the more likely it is that someone
can help you! For example, the following is an example of a very good bug
report (it should of course be posted with the mysqlbug script):
Example run using the mysql command line tool (note the use of the
\G statement terminator for statements whose output width would
otherwise exceed that of an 80-column display device):
mysql> SHOW VARIABLES;
mysql> SHOW COLUMNS FROM ...\G
<output-from-SHOW-COLUMNS>
mysql> EXPLAIN SELECT ...\G
<output-from-EXPLAIN>
mysql> FLUSH STATUS;
mysql> SELECT ...;
<A short version of the output from SELECT,
including the time taken to run the query>
mysql> SHOW STATUS;
<output from SHOW STATUS>
mysqladmin variables extended-status processlist in your mail to
provide some information of how your system is performing!
ftp to
transfer it to ftp://www.mysql.com/pub/mysql/secret/. If the data are
really top secret and you don't want to show them even to us, then go ahead
and provide an example using other names, but please regard this as the last
choice.
mysqld
daemon and that you use to run any MySQL client programs. The
options to programs like mysqld and mysql, and to the
configure script are often keys to answers and very relevant! It is
never a bad idea to include them anyway! If you use any modules, such as
Perl or PHP, please include the version number(s) of those as well.
mysqldump and create a `README' file
that describes your problem.
Create a compressed archive of your files using
tar and gzip or zip, and use ftp
to transfer the archive to ftp://www.mysql.com/pub/mysql/secret/.
Then send a short description of the problem to mysql@lists.mysql.com.
mysqlaccess, the output of mysqladmin reload and all
the error messages you get when trying to connect! When you test your
privileges, you should first run mysqlaccess. After this, execute
mysqladmin reload version, and last you should try to connect with the
program that gives you trouble. mysqlaccess can be found in the
`bin' directory under your MySQL installation directory.
parse error, please check your syntax closely! If
you can't find something wrong with it, it's extremely likely that your
current version of MySQL doesn't support the query you are
using. If you are using the current version and the manual at
http://www.mysql.com/doc.html doesn't cover the syntax you are
using, MySQL doesn't support your query. In this case, your
only options are to implement the syntax yourself or email
If the manual covers the syntax you are using, but you have an older version
of MySQL, you should check the MySQL change history to see
when the syntax was implemented. See section D MySQL change history. In this case, you have the
option of upgrading to a newer version of MySQL.
myisamchk.
See section 13 Maintaining a MySQL installation.
mysqld should
NEVER crash a table if nothing killed it in the middle of an
update! If you can find the source of why mysqld dies, it's much
easier for us to provide you with a fix for the problem!
If you are a support customer, please cross-post the bug report to the appropriate mailing list to see if someone else has experienced (and perhaps solved) the problem.
For information on reporting bugs in MyODBC, see section 16.3 How to report problems with MyODBC.
For solutions to some common problems, see See section 18 Problems and common errors.
When answers are sent to you individually and not to the mailing list, it is considered good etiquette to summarize the answers and send the summary to the mailing list so that others may have the benefit of responses you received that helped you solve your problem!
If you consider your answer to have broad interest, you may want to post it to the mailing list instead of replying directly to the individual who asked. Try to make your answer general enough that people other than the original poster may benefit from it. When you post to the list, please make sure that your answer is not a duplication of a previous answer.
Try to summarize the essential part of the question in your reply; don't feel obliged to quote the entire original message.
Please don't post mail messages from your browser with HTML mode turned on! Many users doesn't read mail with a browser!
This chapter describes MySQL licensing and support arrangements, including:
The formal terms of the license for non-Microsoft operating systems such as Unix or OS/2 are specified in section J The MySQL server license for non Microsoft operating systems. Basically, our licensing policy is as follows:
mysqld server. However, a
multiple-CPU machine counts as a single machine, and there is no restriction
on the number of MySQL servers that run on one machine, or on the
number of clients concurrently connected to a server running on that
machine!
mysql command line client includes code from the readline
library that is under the GNU Public License.
myisampack utility for creating fast compressed read-only
databases. (The server includes support for reading such databases but
not the packing tool used to create them.) When support agreements
generate sufficient revenue, we will release this tool under the same
license as the MySQL server.
For use under Microsoft operating systems (Win95/Win98/WinNT), you need a MySQL license after a trial period of 30 days, with the exception that licenses may be obtained upon request at no cost for educational use or for university- or government-sponsored research settings. See section K The MySQL license for Microsoft operating systems. A shareware version of MySQL-Win32 that you can try before buying is available at http://www.mysql.com/mysql_w32.htmy. After you have paid, you will get a password that will enable you to access the newest MySQL-Win32 version.
If you have any questions as to whether or not a license is required for your particular use of MySQL, please contact us. See section 3.5.2 Contact information.
If you require a MySQL license, the easiest way to pay for it is to use the license form at TcX's secure server at https://www.mysql.com/license.htmy. Other forms of payment are discussed in section 3.5.1 Payment information.
There are several different copyrights on the MySQL distribution:
mysqlclient
library and programs in the `client' directory is in the public
domain. Each file that is in the public domain has a header which clearly
states so. This includes everything in the `client' directory and some parts of
the mysys, mystring and dbug libraries.
getopt) are covered by the
``GNU LIBRARY LIBRARY GENERAL PUBLIC LICENSE''. See the
`mysys/COPYING.LIB' file.
readline) are covered by the
``GNU GENERAL PUBLIC LICENSE''. See the `readline/COPYING' file.
regexp library) are covered by a Berkeley
style copyright.
The following points set forth the philosophy behind our copyright policy:
We may choose to distribute older versions of MySQL with the GPL in the future. However, these versions will be identified as GNU MySQL. Also, all copyright notices in the relevant files will be changed to the GPL.
This section is a clarification of the license terms that are set forth in the ``MySQL FREE PUBLIC LICENSE'' (FPL). See section J The MySQL server license for non Microsoft operating systems.
MySQL may be used freely, including by commercial entities for evaluation or unsupported internal use. However, distribution for commercial purposes of MySQL, or anything containing or derived from MySQL in whole or in part, requires a written commercial license from TcX AB, the sole entity authorized to grant such licenses.
You may not include MySQL ``free'' in a package containing anything for which a charge is being made, except as noted below.
The intent of the exception provided in the second clause of the license is to allow commercial organizations operating an FTP server or a bulletin board to distribute MySQL freely from it, provided that:
If you want to distribute software in a commercial context that incorporates MySQL and you do not want to meet these conditions, you should contact TcX AB to find out about commercial licensing, which involves a payment. The only ways you legally can distribute MySQL or anything containing MySQL are by distributing MySQL under the requirements of the FPL, or by getting a commercial license from TcX AB.
This section describes some situations illustrating whether or not you must license the MySQL server. Generally these examples involve providing MySQL as part of a product or service that you are selling to a customer, or requiring that MySQL be used in conjunction with your product. In such cases, it is your responsibility to obtain a license for the customer if one is necessary. (This requirement is waived if your customer already has a MySQL license. But the seller must send customer information and the license number to TcX, and the license must be a full license, not an OEM license.)
Note that a single MySQL license covers any number of
CPUs/users/customers/mysqld servers on a machine!
To determine whether or not you need a MySQL license when selling your application, you should ask whether the proper functioning of your application is contingent on the use of MySQL and whether you include MySQL with your product. There are several cases to consider:
mysqld server. For example, if you've designed your
application around MySQL, then you've really made a commercial
product that requires the engine, so you need a license.
If your application does not require MySQL, you need not obtain a
license. For example, if MySQL just added some new optional
features to your product (such as adding logging to a database if
MySQL is used rather than logging to a text file), it should fall
within normal use, and a license would not be required.
In other words, you need a license if you sell a product designed
specifically for use with MySQL or that requires the MySQL
server to function at all. This is true whether or not you provide
MySQL for your client as part of your product distribution.
It also depends on what you're doing for the client. Do you plan to provide
your client with detailed instructions on installing MySQL with your
software? Then your product may be contingent on the use of MySQL;
if so, you need to buy a license. If you are simply tying into a database
that you expect already to have been installed by the time your software is
purchased, then you probably don't need a license.
mysqld server,
because in this case you are selling a system that includes MySQL.
This is true whether the use of MySQL with your product
is required or optional.
If you perform MySQL installation on a client's machine and any money changes hands for the service (directly or indirectly), then you must buy a MySQL license.
If you sell an application for which MySQL is not strictly required but can be used, a license may be indicated, depending on how MySQL is set up. Suppose your product neither requires MySQL nor includes it in your product distribution, but can be configured to use MySQL for those customers who so desire. (This would be the case, for example, if your product can use any of a number of database engines.)
If the customer obtains and installs MySQL, no license is needed. If you perform that service for your customer, then a license is needed because then you are selling a service that includes MySQL.
Internet Service Providers (ISPs) often host MySQL servers for their customers.
If you are an ISP that allows customers to install and administer MySQL for themselves on your machine with no assistance from you, neither you nor your customer need a MySQL license.
If you charge for MySQL installation and administrative support as part of your customer service, then you need a license because you are selling a service that includes MySQL.
If you use MySQL in conjunction with a web server, you don't have to pay for a license.
This is true even if you run a commercial web server that uses MySQL, since you are not selling MySQL itself. However, in this case we would like you to purchase MySQL support, because MySQL is helping your enterprise.
Our current license prices are shown below. All prices are in US Dollars. If you pay by credit card, the currency is EURO (European Union Euro) so the prices will differ slightly.
| Number of licenses | Price per copy | Total |
| 1 | US $200 | US $200 |
| 10 pack | US $150 | US $1500 |
| 50 pack | US $120 | US $6000 |
For high volume (OEM) purchases, the following prices apply:
| Number of licenses | Price per copy | Minimum at one time | Minimum payment |
| 100-999 | US $40 | 100 | US $4000 |
| 1000-2499 | US $25 | 200 | US $5000 |
| 2500-4999 | US $20 | 400 | US $8000 |
For OEM purchases, you must act as the middle-man for eventual problems or extension requests from your users. We also require that OEM customers have at least an extended email support contract.
If you have a low-margin high-volume product, you can always talk to us about other terms (for example, a percent of the sale price). If you do, please be informative about your product, pricing, market and any other information that may be relevant.
After buying 1 MySQL license, you will get a personal copy of
the myisampack utility. You are not allowed to redistribute this
utility but you can distribute tables packed with it.
A full-price license is not a support agreement and includes very minimal support. This means that we try to answer any relevant question. If the answer is in the documentation, we will direct you to the appropriate section. If you have not purchased a license or support, we probably will not answer at all.
If you discover what we consider a real bug, we are likely to fix it in any case. But if you pay for support we will notify you about the fix status instead of just fixing it in a later release.
More comprehensive support is sold separately. Descriptions of what each level of support includes are given in section 3.6 Types of commercial support. Costs for the various types of commercial support are shown below. Support level prices are in EURO (European Union Euro). One EURO is about 1.17 USD.
| Type of support | Cost per year |
| Basic email support | EURO 170 |
| Extended email support | EURO 1000 |
| Login support | EURO 2000 |
| Extended login support | EURO 5000 |
You may upgrade from any lower level of support to a higher level of support for the difference between the prices of the two support levels.
Currently we can take SWIFT payments, cheques or credit cards.
Payment should be made to:
Postgirot Bank AB 105 06 STOCKHOLM, SWEDEN TCX DataKonsult AB BOX 6434 11382 STOCKHOLM, SWEDEN SWIFT address: PGSI SESS Account number: 96 77 06 - 3
Specify: license and/or support and your name and email address.
In Europe and Japan you can use EuroGiro (that should be less expensive) to the same account.
If you want to pay by cheque, make it payable to ``Monty Program KB'' and mail it to the address below:
TCX DataKonsult AB BOX 6434, Torsgatan 21 11382 STOCKHOLM, SWEDEN
If you want to pay by credit card over the Internet, you can use TcX's secure license form.
You can also print a copy of the license form, fill it in and send it by fax to:
+46-8-729 69 05
If you want us to bill you, you can use the license form and write ``bill us'' in the comment field. You can also mail a message to with your company information and ask us to bill you.
For commercial licensing, or if you have any questions about any of the information in this section, please contact the MySQL licensing team. The much preferred method is by E-Mail to these may take much longer (Fax +46-8-729 69 05).
David Axmark Detron HB Kungsgatan 65 B 753 21 UPPSALA SWEDEN Voice Phone +46-18-10 22 80 (Timezone GMT+1. Swedish and English spoken)
Basic email support is a very inexpensive support option and should be thought of more as a way to support our development of MySQL than as a real support option.
At this support level, the MySQL mailing lists are the preferred means of communication. Questions normally should be mailed to the primary mailing list (mysql@lists.mysql.com) or one of the other regular lists (for example, mysql-win32@lists.mysql.com for Windows-related MySQL questions), as someone else already may have experienced and solved the problem you have. See section 2.2 Asking questions or reporting bugs.
However, by purchasing basic email support, you also have access to the support address mysql-support@mysql.com, which is not available as part of the minimal support that you get by purchasing a MySQL license. This means that for especially critical questions, you can cross-post your message to mysql-support@mysql.com. (If the message contains sensitive data, you should post only to mysql-support@mysql.com.)
REMEMBER! to ALWAYS include your registration number and expiration date when you send a message to
Basic email support includes the following types of service:
myisampack packing tool for
creating fast compressed read-only databases. The current server includes
support for reading such databases but not the packing tool used to
create them.
Extended email support includes everything in basic email support with these additions:
mysqld for your situation.
Login support includes everything in extended email support with these additions:
kill -9 command).
Extended login support includes everything in login support with these additions:
mysql> select MY_CALCULATION(col_name1,col_name2) from tbl_name;
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
Brazil [Matrix]
Chile [Vision]
South-Africa [Mweb/]
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to webmaster@mysql.com.
Europe:
Austria [Univ. of Technology/Vienna]
WWW
FTP
Bulgaria [Naturella]
FTP
Croatia [HULK]
WWW
FTP
Czech Republic [Masaryk University in Brno]
WWW
FTP
Czech Republic [www.sopik.cz]
WWW
Denmark [Borsen]
WWW
Denmark [SunSITE]
WWW
FTP
Estonia [OKinteractive]
WWW
France [minet]
WWW
Finland [EUnet]
WWW
Finland [clinet]
FTP
Germany [Bonn University, Bonn]
WWW
FTP
Germany [Wolfenbuettel]
WWW
FTP
Germany [Staufen]
WWW
Germany [Cable & Wireless]
FTP
Greece [NTUA, Athens]
WWW
FTP
Island [GM]
WWW
WWW
Italy [Teta Srl]
WWW
Ireland [Ireland On-Line/Dublin]
WWW
FTP
Poland [Sunsite]
WWW
FTP
Portugal [lerianet]
WWW
FTP
Russia [DirectNet]
WWW
Russia [IZHCOM]
WWW
FTP
Russia [Scientific Center/Chernogolovka]
FTP
Romania [Timisoara]
WWW
FTP
Romania [Bucharest]
WWW
FTP
Spain [MasterD]
WWW
Sweden [Sunet]
WWW
FTP
Switzerland [Sunsite]
WWW
FTP
UK [Omnipotent/UK]
WWW
FTP
UK [PLiG/UK]
WWW
FTP
UK [SunSITE]
WWW
FTP
Ukraine [PACO]
WWW
FTP
North America:
Canada [Tryc]
WWW
Canada [Cyberus]
WWW
FTP
USA [Hurricane Electric/San Jose]
WWW
USA [Meltzer/New York State]
FTP
USA [Circle Net/North Carolina]
WWW
USA [Gina net/Florida]
WWW
USA [Wisconsin University/Wisconsin]
WWW
FTP
USA [DIGEX]
FTP
South America:
Asia:
China [Freecode]
WWW
China [Netfirm]
WWW
Korea [KREONet]
WWW
Japan [Soft Agency]
WWW
Japan [Nagoya Syouka University]
WWW
FTP
Singapore [HJC]
WWW
FTP
Taiwan [HT]
WWW
Australia:
Australia [AARNet/Queensland]
WWW
FTP
Australia [Blue Planet/Melbourne]
WWW
Australia [ITworks Consulting/Victoria]
WWW
Africa:
We use GNU Autoconf so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (versions 2.5 & 2.6) and to a lesser extent on RedHat Linux 5.0.
MySQL has been reported to compile sucessfully on the following operating system/thread package combinations. Note that for many operating systems, the native thread support works only in the latest versions.
glibc 2.0.7
The first decision to make is whether you want to use the latest development release or the last stable release:
crash-me and
benchmark tests.
See section 10.8 Using your own benchmarks.
The second decision to make is whether you want to use a source distribution or a binary distribution:
The MySQL naming scheme uses release numbers that consist of three
numbers and a suffix. For example, a release name like
mysql-3.21.17-beta is interpreted like this:
3) describes the file format. All
version 3 releases have the same file format. When a version 4 appears, every
table will have to be converted to the new format (nice tools for this will
be included, of course).
21) is the release level. Normally there are two to
choose from. One is the release/stable branch (currently 21) and the
other is the development branch (currently 22) . Normally both are
stable, but the development version may have quirks, missing documentation on
new features or may fail to compile on some systems.
17) is the version number within the
release level. This is incremented for each new distribution. Usually you
want the latest version for the release level you have choosen.
beta) indicates the stability level of
the release. The possible suffixes are:
alpha indicates that the release contains some large section of
new code that hasn't been 100% tested. Known bugs (usually there are none)
should be documented in the News section. See section D MySQL change history. There are also new
commands and extensions in most alpha releases.
beta means that all new code has been tested. No major new features
were added. There should be no known bugs.
gamma is a beta that has been around a while and seems to work fine.
This is what many other companies call a release.
All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Since the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.
Note that all releases have been tested at least with:
This chapter describes how to obtain and install MySQL:
Check the MySQL home page for information about the current version and for downloading instructions.
However, the Internet connection at TcX is not so fast; we would prefer that you do the actual downloading from one of the mirror sites listed below.
Please report bad or out of date mirrors to