FAQ – Bug reporting

MySQL Workbench FAQ Listing

This is a collection of the questions that have been asked frequently.

Bug reporting

Q.1: Where can I report bugs and see existing bug reports?Please, use our dedicated site for this. You’ll have to register before reporting bugs. There you can also make search among existing bug reports & see their status. To make simplest search, it will be enough to select appropriate category, e.g. “MySQL Workbench/OSS Edition”, and type keywords of interest. List of weighted tags may help you to select keywords, however it contains tags related to all MySQL products (mostly for DBMS), not only MySQL Workbench.Q.2: Where can I report feature requests and see existing feature requests?The same site is used for both bug reports & feature requests. To register request you need to initiate bug report and mark its severity to “Feature request”. Search is to be done the same way it’s done for bug reports, but additionally you’ll have to set severity criterion to “Feature request”.Q.3: Are there any special requirements for bug reports in case of Workbench?Please follow these guidelines when filling new bug report:

  1. If you anticipate that defect, being reported, relates to DBMS in some way or you are not certain about this, please provide DBMS version as well.
  2. Workbench passes numerous (apparently still not enough though) automatic and manual tests before release. That’s why simply telling “this or that thing doesn’t work” often doesn’t provide enough info to fix the problem. Please provide more details on context when you fill it’s related to the problem. In case of reverse-engineering that could be original SQL statements or results of `show create` command for problematic objects. When it goes about low level rendering issues, you will help us if provide also max hardware supported version of OpenGL, model of video card and version of OS. Finally send saved Workbench document by the need. Additional info will never hurt but always may help to avoid odd round trips and decrease time needed to fix the bug.
  3. Isolate problems when necessary, don’t mix several unrelated problems in one big bug report, rather split them.
  4. Try to narrow the problem as much as possible. By selecting tags and subject carefully the problem has more chances to be noted by right person quickly.
  5. You may always request new feature by marking bug report status as such. Please make difference when appropriate.

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.