Dyntex.net Support Centre: MySQL Reference Manual p.72

<< previous page -- table of contents -- next page >>

Chapter_1

Chapter_2

Chapter_3

Chapter_4

Chapter_5

Return to Table of Contents

Table of Contents
1. General Information
2. MySQL Installation
3. Tutorial Introduction
4. Database Administration
5. MySQL Optimisation
6. MySQL Language Reference
7. MySQL Table Types
8. MySQL APIs
9. Extending MySQL

72 MySQL Technical Reference for Version 4.0.3 Otherwise, if you are running an old system and want to upgrade, but don't want to take chances with a non-seamless upgrade, you should upgrade to the latest in the same branch you are using (where only the last version number is newer than yours). We have tried to x only fatal bugs and make small, relatively safe changes to that version. The second decision to make is whether you want to use a source distribution or a binary distribution. In most cases you should probably use a binary distribution, if one exists for your platform, as this generally will be easier to install than a source distribution. In the following cases you probably will be better o with a source installation: If you want to install MySQL at some explicit location. (The standard binary distribu- tions are \ready to run" at any place, but you may want to get even more exibility). To be able to satisfy dierent user requirements, we are providing two dierent binary versions: one compiled with the non-transactional table handlers (a small, fast binary), and one congured with the most important extended options like transaction-safe tables. Both versions are compiled from the same source distribution. All native MySQL clients can connect to both MySQL versions. The extended MySQL binary distribution is marked with the -max sux and is cong- ured with the same options as mysqld-max. See Section 4.7.5 [mysqld-max], page 285. If you want to use the MySQL-Max RPM, you must rst install the standard MySQL RPM. If you want to congure mysqld with some extra features that are not in the standard binary distributions. Here is a list of the most common extra options that you may want to use: --with-innodb --with-berkeley-db --with-raid --with-libwrap --with-named-z-lib (This is done for some of the binaries) --with-debug[=full] The default binary distribution is normally compiled with support for all character sets and should work on a variety of processors from the same processor family. If you want a faster MySQL server you may want to recompile it with support for only the character sets you need, use a better compiler (like pgcc), or use compiler options that are better optimised for your processor. If you have found a bug and reported it to the MySQL development team you will probably receive a patch that you need to apply to the source distribution to get the bug xed. If you want to read (and/or modify) the C and C++ code that makes up MySQL, you should get a source distribution. The source code is always the ultimate manual. Source distributions also contain more tests and examples than binary distributions. The MySQL naming scheme uses release numbers that consist of three numbers and a sux. For example, a release name like mysql-3.21.17-beta is interpreted like this: The rst number (3) describes the le format. All Version 3 releases have the same le format.

MySQL Reference Manual

Our Partners

SpiritHost - web hosting for spiritual and education sites
SpiritHit.com - Religious and Spiritual Portal

Return to Table of Contents	Back to top

Web Hosting: Manuals & FAQ's

1. Unix-Based Web Hosting
2. Unix Dedicated Servers
3. Windows Dedicated Servers
4. CuteFTP User’s Guide
5. CuteHTML User’s Guide
6. WS_FTP Pro User's Guide
7. Miva Order User's Guide
8. Miva Merchant User's Guide