Go to the first, previous, next, last section, table of contents.
If you can, please use the `mysqlbug' script that can be found in
the scripts directory in the distribution. If that is not possible,
remember to specify (if relevant) the following. Note that it is
possible to answer a letter with too much information but not one with too
little. You should always use `mysqlbug' if your question is anyway
related to a MySQL version you are using!
mysqlbug should automaticly finds most of the following information, but if
something important missing please include this in your question!
-
State which version of MySQL you are using (for example
mysql-3.21..tgz). You can find out which version you are running by
typing
mysqladmin version.
-
The manufacturer and model of machine you are working on.
-
The operating system. For most operating systems you can get this from
uname -a.
-
Sometimes the amount of memory (real and virtual) is also relevant.
-
Write in the mail that you have checked the reference manual and
mail archive so others know that you have tried to solve your
problem yourself.
-
If this is a bug when compiling: Include the exact error messages and
also a few lines around the offending code in the file from which you
got the error.
-
If this is a run-time bug, please describe exactly how you got the
error. If you can include a test program, with tables, which shows the error
you will probably get a more explicit answer.
-
f the you can't produce a test case in a few rows or if the the test table
is too big to be mailed to everyone (more than 10 rows) you should
make a mysqldump of your tables and make a README that describes your
problem. Tar and gzip or zip the files and ftp the archive to
ftp://www.tcx.se/pub/mysql/hidden. Send after this a short description of
the problem to mysql@tcx.se
-
If the questions is related to the privilege system, please include
the output of mysqlaccess, the output of 'mysqladmin reload' and
and all error messages you get when trying to connect ! You should do
the test in the above order !
If you are a support customer, please post the bug report to the
specified mailing list for higher priority treatment.
When answers are sent to you individually and not to the mailing list,
it is considered good etiquette to summarise the answers and mail them
to the mailing list.
Go to the first, previous, next, last section, table of contents.