MySQL Chinese Reference Manual 3 (Mysql Mail List and How to Questions or Report Errors)
Translator: 子
〖
Back to〗 Forward〗
Translator: Clyan@sohu.com) Home: http://linuxdb.yeah.net2 mysql Mail list and how to ask questions or report Errors 2.1 mysql mailing list To subscribe to the primary mysql mailing list, send a message to email address MySQL -Subscribe@lists.mysql.com. To unsubscribe the list of MYSQL mail, send a message to email address mysql-unsubscribe@lists.mysql.com. Only the address you send messages is meaningful, the subject line and the text of the message will be ignored. If your reply address is not valid, you can specify the address clearly. Put your short to the subscription or unsubscribe command word, then your address, "@" is replaced by a character "=". For example, to subscribe to john@host.domain, send a message to mysql-subscribe-john=host.domain@lists.mysql.com. Mail to mysql-subscribe@lists.mysql.com or ezmlm mailing list processor. Details can be obtained at the EZMLM outlet. Have you want to send a message to the raft old 恚 ⑺ 愕 南 ⒌? A href = mailto: mysql@lists.mysql.com> mysql@lists.mysql.com. However, don't send messages about subscription or unsubscribe to mysql@lists.mysql.com, because any email sent to this address is automatically distributed to thousands of other users. Your local website may have a lot of mysql@lists.mysql.com's subscribers, and if so, there may be a list of local mailing so that the message from lists.mysql.com is sent to your local list. In this case, please contact your system executive to join the local MySQL list and delete it from it. There is a list of Mysql mailing: Announce This is a new version of MySQL and the publishing notification of related programs. This is a list of small information, and we think that all MySQL users should subscribe. MySQL is the main list of general mysql discussion. Please note that some topics are best discussed on a more professional list. If you mail to a list of errors, you may not have an answer! MySQL Digest Digest form of MySQL list, which means you get all a single message, as a big email sends once a day. Java discusses mysql and java, mainly about JDBC drivers. Java Digest A list of Digests Java. Win32 is a MySQL everything on Microsoft operating systems such as Windows NT. Win32 Digest A Digest Version Win32 Table. Myodbc is related to all things of MySQL with ODBC. Myodbc Digest A Digest Version Myodbc list. MSQL-MySQL-Modules About a list of Perl supports in MySQL. MSQL-MySQL-MODULES-Digest A Digest Version MSQL-MySQL-MODULES list. Developer is a list of people who develop MySQL original code. Developer Digest a list of Digest version. You can subscribe or unused all lists with the above method. In your subscription or unsubscribe message, just put it in the appropriate mail list name of MySQL. For example, subscribe or unsubscribe the Myodbc list, send a message to (the original text is not available).
2.2 Questions or report errors Before mailing a wrong report or problem, please do it: http://www.mysql.com/manual_chapter/manual_toc.html We have found new discoveries Solution to the problem to update the manual, try to make it the latest! Search Mysql Mail List Profile: http://www.mysql.com/doc.html You can also use http://www.mysql.com/search.html to find at http://www.mysql.com/ Web pages (including manuals). If you can't find the answer in the manual or archive, check your local MySQL expert. If you still can't find your question, continue to read the next section on how to send an email (the original text is not available). 2.3 How to report errors or problems to write a good error report requires patience, but for the first time, you can save you my time. This section will help you write your report correctly so that you may not waste time, or you may not help us at all. If possible, we encourage everyone to generate an error report (or a report on any problem) using the MySQLbug script (or a report on any problem). MySQLBUG can be found in the 'scripts' directory in the 'bin' directory in the source code distribution or binary mysql installation directory. If you can't use mysqlbug, you should still include all the necessary information listed in this section. MySqlbug scripts help you generate a report by automatically identifying many of the following information, but if some important things are gone, please include it in your message! Please read this section carefully and guarantee that all information described here is included in your report. To remember, it is possible to reply to a message containing too much information, but does not reply to include very little information, because people think they know the cause of a problem and assume some details, they often ignore the facts. A good principle is: If you suspect what you say, continue! Write a few lines in your report, which is forced to ask questions and wait for the answer to a thousand times more than the first time without having enough information. The most common mistake is that people don't point out the version number of the MySQL distribution they are using, or do not point out on what platform is installed on what platform installed Mysql (including the platform version number). This is extremely relevant, and there is no 99% error report! We often get such a question "Why don't it work?", Then we find that the required features have not implemented in this version of MySQL, or an error described in a report is already updated in MySQL version correction . Sometimes the error is dependent on the platform. In this case, I don't know if the platform operating system and version number are not possible to fix anything. Also remember, provide your compiler information if it is related to the question. People often find mistakes that I think Mysql in the compiler. Most compilers are always developed and multi-version gradually become better. In order to determine if you decide whether your problem relies on your compiler, we need to know what compiler that is used. Note that each compiler has a problem that should be considered an error, so you want to report. In the error report, the integrity describes the most helpful description. That is, you have made a good example of this problem and the exact problem itself. The best report is to include a complete example of how to generate errors or problems again. If a program produces an error message, it is very important to include it in your error report! If we try to find something from the file from the program, it is best to accurately match the program's error messages.
(Even note case!) You should never try to remember what the error message is, reverse, copy all messages and paste into your report! If you have a Myodbc problem, you should try to generate a MyodBC trace file, see 16.6 Report Myodbc problem. Please remember that there will be a lot of 80 columns that you want to read. When generating an example or using the MySQL command line tool, you should use the -vertical option (or the G statement terminator) for those outputs that may exceed the displayable width (for example, the example, see below). Please include the following information in your report: The version number of the MySQL distribution (for example, MySQL 3.22.22). You can perform mysqladmin version to find which version you are running. MySQLADMIN can be found in the 'bin' directory of your MySQL installation directory. The manufacturer and model of the machine you are using. Operating system names and versions. For most operating systems, you can get the information by executing a UNIX command uname -a. Sometimes the amount of memory (physical and virtual) is meaningful, if you have any questions, contain these values. If you are using a MySQL source code distribution, you need to use the name and version number of the compiler. If you have a binary code distribution, you need the name of the distribution. If the problem occurs during compilation, an accurate error message is included, and some contexts around the error code occurred in the file occurred. If any database table is related to the problem, contains the output result from MySQLDUMP - DB_NAME TBL_NAME1 TBL_NAME2 .... This is easy to do, and it is an effective way to get any database table information, which will help us create a problem that matches what you have encountered. For questions related to speed or SELECT statement, you should always include Explain Select. . . The output and the number of rows generated by at least the SELECT statement. You give more information about your situation, the more people can help you. For example, the following example is a good error report (of course, it should be mailed to the mysqlbug script): Run an example of the mysql command line tool (Note that the statement to output more than 80 columns display device uses G terminator): mysql > Show variables; mysql> show columns from ... g
When a problem is given, it is best to use instead of a new variable name, a table name, and so on. This issue should be related to the name, table, etc. of a variable! Perhaps these conditions are harsh, but safety is better than worrying. Anyway, providing examples of using your actual situation should be relatively easy, and in all respects it is better to us. If you don't want to display someone else, you can upload it to ftp://www.mysql.com/pub/mysql/secret/. If the data is indeed highly confidential, don't even want us to see them, then continue, and provide examples of other names, but note that this is the final selection. If possible, including all options for related programs, for example, indicating that you start the MySQLD daemon and run any of the options used by any MySQL client, the objects, Mysqld and MySQL, and Configure are often the key and critical for the answer! Including them is definitely not a bad idea! If you use any modules, such as Perl or PHP, include their version number. If you can't generate a test of a number of rows, or if the test table is too big, you cannot send a list of mailing (more than 10 lines), you should use the mysqldump false (dump) database table and create a "Readme" file to describe your question Use tar and gzip to create a compressed file for your file, and transfer the file file to ftp://www.mysql.com/pub/mysql/secret/, then send a short description of the problem to mysql @ lists.mysql.com. If your problem is related to the permission system. Please include Mysqlaccess, MySQLADMIN RELOAD output and all error messages that are trying to connect! When you test your permissions, you should first run mysqlaccess. After this, execute the mysqladmin reload version, and finally you should try to connect with the program you have problems. MySQLACCESS is found in the "bin" directory in your mysql installation directory. If you have a patch for the wrong, it is best, but don't assume that the patch is everything we need, or you can use it even if you don't provide some necessary information such as patch, you can use it. We may find your patch problem, or we may not understand it at all. If so, we can't use it. Here the test conditions will help us, which means that the patch will process all possible situations. If we discover the boundary conditions that the patch can't work (even very blame), it may be useless. What is wrong with the error, why or it relies on what is usually wrong. We can't even do this speculation when you don't use a debugger to determine a true cause of an error. In your email message, you have checked the reference manual and email archiving so that others know that you try to solve your problem. If you get a PARSE Error, please check your grammar carefully! If you can't find anything wrong, it is very likely that your current MySQL version does not support the query you are using. If you are using the latest version and http://www.mysql.com/doc.html's reference manual does not involve the syntax you are using, MySQL does not support your query. In this case, your unique choice is to realize the syntax and mailed it. If the manual involves the grammar you are using, you have an older version of MySQL, you should check when Mysql's update history to find when it is implemented. See D MySQL Change History. At this point you have the choice of upgrading to an update MySQL version.
