To subscribe to the main MySQL mailing list, send a message to the electronic mail address firstname.lastname@example.org.
To unsubscribe from the main MySQL mailing list, send a message to the electronic mail address email@example.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
firstname.lastname@example.org, send a message
Mail to email@example.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
firstname.lastname@example.org. However, please do not send mail about
subscribing or unsubscribing to email@example.com, since any
mail sent to that address is distributed automatically to thousands of other
Your local site may have many subscribers to firstname.lastname@example.org.
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:
mysqllist in digest form. That means you get all individual messages, sent as one large mail message once a day.
bugslist in digest form
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:
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.
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.
If you can make a test case which clearly shows the bug, you should post it the the email@example.com list. Note that on this list you should only post a full, repeatable bug report, using the mysqlbug script (if not running on Windows, in which case one should include a description of the operating system and the MySQL version). You should preferable test the problem using the latest stable or development version of MySQL before posting! Anyone should be able to repeat the bug by just using 'mysql test < script' on the included test case. All bugs posted on this list will be corrected or documented in the next MySQL release! If there was only small code changes involved we will also post a patch that fixes the problem.
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
mysql command line tool, you should therefore use
--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
Please include the following information in your report:
mysqladmincan be found in the `bin' directory under your MySQL installation directory.
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.
SELECTstatements, you should always include the output of
EXPLAIN SELECT ..., and at least the number of rows that the
SELECTstatement 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
mysqlbugscript): Example run using the
mysqlcommand line tool (note the use of the
\Gstatement 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 processlistin your mail to provide some information of how your system is performing!
ftpto 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.
mysqlddaemon and that you use to run any MySQL client programs. The options to programs like
mysql, and to the
configurescript 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.
mysqldumpand create a `README' file that describes your problem. Create a compressed archive of your files using
zip, and use
ftpto transfer the archive to ftp://www.mysql.com/pub/mysql/secret/. Then send a short description of the problem to firstname.lastname@example.org.
mysqlaccess, the output of
mysqladmin reloadand 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.
mysqlaccesscan 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.
mysqldshould NEVER crash a table if nothing killed it in the middle of an update! If you can find the source of why
mysqlddies, 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!
Go to the first, previous, next, last section, table of contents.