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

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

26 MySQL Technical Reference for Version 4.0.3 Start by searching the MySQL online manual at: http://www.mysql.com/doc/ We try to keep the manual up to date by updating it frequently with solutions to newly found problems! Search the MySQL mailing list archives: http://lists.mysql.com/ You can also use http://www.mysql.com/search.html to search all the web pages (including the manual) that are located at http://www.mysql.com/. If you can't nd an answer in the manual or the archives, check with your local MySQL expert. If you still can't nd an answer to your question, go ahead and read the next section about how to send mail to mysql@lists.mysql.com. 1.6.2.3 How to Report Bugs or Problems Writing a good bug report takes patience, but doing it right the rst time saves time for us and for you. A good bug report containing a full test case for the bug will make it very likely that we will x it in the next release. 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. The normal place to report bugs and problems is mysql@lists.mysql.com. If you can make a test case that clearly demonstrates the bug, you should post it to the bugs@lists.mysql.com list. Note that on this list you should only post a full, repeatable bug report using the mysqlbug script. If you are running on Windows, you should include a description of the operating system and the MySQL version. Preferably, you should test the problem using the latest stable or development version of MySQL Server before posting! Anyone should be able to repeat the bug by just using \mysql test < script" on the included test case or run the shell or Perl script that is included in the bug report. All bugs posted on the bugs list will be corrected or documented in the next MySQL release! If only small code changes are needed to correct this problem, we will also post a patch that xes the problem. If you have found a sensitive security bug in MySQL, you should send an e-mail to security@mysql.com. 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

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