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

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

30 MySQL Technical Reference for Version 4.0.3 mented. In this case, you have the option of upgrading to a newer version of MySQL Server. See Appendix D [News], page 675. If you have a problem such that your data appears corrupt or you get errors when you access some particular table, you should rst check and then try repairing your tables with myisamchk or CHECK TABLE and REPAIR TABLE. See Chapter 4 [MySQL Database Administration], page 181. If you often get corrupted tables you should try to nd out when and why this happens. In this case, the `mysql-data-directory/'hostname'.err' le may contain some in- formation about what happened. See Section 4.9.1 [Error log], page 308. Please include any relevant information from this le in your bug report. Normally mysqld should never crash a table if nothing killed it in the middle of an update! If you can nd the cause of mysqld dying, it's much easier for us to provide you with a x for the problem. See Section A.1 [What is crashing], page 627. If possible, download and install the most recent version of MySQL Server and check whether it solves your problem. All versions of the MySQL software are thoroughly tested and should work without problems. We believe in making everything as backward-compatible as possible, and you should be able to switch MySQL versions without any hassle. See Section 2.2.3 [Which version], page 71. If you are a support customer, please cross-post the bug report to mysql-support@mysql.com for higher-priority treatment, as well as 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 8.3.4 [ODBC Problems], page 549. For solutions to some common problems, see Appendix A [Problems], page 627. When answers are sent to you individually and not to the mailing list, it is considered good etiquette to summarise the answers and send the summary to the mailing list so that others may have the benet of responses you received that helped you solve your problem! 1.6.2.4 Guidelines for Answering Questions on the Mailing List 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 benet from it. When you post to the list, please make sure that your answer is not a duplication of a previous answer. Try to summarise 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 don't read mail with a browser! 1.7 How Standards-compatible Is MySQL? This section describes how MySQL relates to the ANSI SQL standards. MySQL Server has many extensions to the ANSI SQL standards, and here you will nd out what they are and

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