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

<< 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

Chapter 1: General Information 7 ODBC (Open-DataBase-Connectivity) support for Win32 (with source). All ODBC 2.5 functions and many others. For example, you can use MS Access to connect to your MySQL server. See Section 8.3 [ODBC], page 546. Localisation The server can provide error messages to clients in many languages. See Section 4.6.2 [Languages], page 269. Full support for several dierent character sets, including ISO-8859-1 (Latin1), german, big5, ujis, and more. For example, the Scandinavian characters '', '' and '' are allowed in table and column names. All data is saved in the chosen character set. All comparisons for normal string columns are case-insensitive. Sorting is done according to the chosen character set (the Swedish way by default). It is possible to change this when the MySQL server is started. To see an example of very advanced sorting, look at the Czech sorting code. MySQL Server supports many dierent character sets that can be specied at compile and runtime. Clients and Tools Includes myisamchk, a very fast utility for table checking, optimisation, and repair. All of the functionality of myisamchk is also available through the SQL interface as well. See Chapter 4 [MySQL Database Administration], page 181. All MySQL programs can be invoked with the --help or -? options to obtain online assistance. 1.2.3 How Stable Is MySQL? This section addresses the questions \How stable is MySQL Server?" and \Can I depend on MySQL Server in this project? " We will try to clarify these issues and answer some important questions that concern many potential users. The information in this section is based on data gathered from the mailing list, which is very active in identifying problems as well as reporting types of use. Original code stems back from the early '80s, providing a stable code base, and the ISAM ta- ble format remains backward-compatible. At TcX, the predecessor of MySQL AB, MySQL code has worked in projects since mid-1996, without any problems. When the MySQL Database Software 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 dierent types of queries from us. Each new release has had fewer portability problems (even though each new release has had many new features). Each release of the MySQL Server has been usable. There have only been problems when users try code from the \gray zones." Naturally, new users don't know what the gray zones are; this section attempts to indicate those that are currently known. The descriptions mostly deal with Version 3.23 of MySQL Server. All known and reported bugs are xed in the latest version, with the exception of those listed in the bugs section, which are things that are design-related. See Section 1.7.5 [Bugs], page 40.

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