Downloads:
566,021
Downloads of v 6.3.10:
322
Last Update:
21 Feb 2018
Package Maintainer(s):
Software Author(s):
- Oracle
Tags:
mysql workbench sql database query browser administrator- Software Specific:
- Software Site
- Software License
- Package Specific:
- Possible Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
MySQL Workbench
- Software Specific:
- Software Site
- Software License
- Package Specific:
- Possible Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
566,021
Downloads of v 6.3.10:
322
Maintainer(s):
Software Author(s):
- Oracle
MySQL Workbench
- 1
- 2
- 3
This Package Contains an Exempted Check
Not All Tests Have Passed
This package was rejected on 28 Mar 2018. The reviewer chocolatey-ops has listed the following reason(s):
MySQL Workbench provides DBAs and developers an integrated tools environment for:
- Database Design and Modeling
- SQL Development (replacing MySQL Query Browser)
- Database Administration (replacing MySQL Administrator)
$packageName = 'mysql.workbench'
$packageSearch = "MySQL Workbench"
$installerType = 'msi'
$silentArgs = '/quiet /qn /norestart'
$validExitCodes = @(0,3010)
Get-ItemProperty -Path @( 'HKLM:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall*',
'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall*',
'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall*' ) `
-ErrorAction:SilentlyContinue `
| Where-Object { $_.DisplayName -like "$packageSearch*" } `
| ForEach-Object { Uninstall-ChocolateyPackage -PackageName "$packageName" `
-FileType "$installerType" `
-SilentArgs "$($_.PSChildName) $silentArgs" `
-ValidExitCodes $validExitCodes }
Log in or click on link to see number of positives.
- mysql-workbench-community-6.3.10-winx64.msi (abb03477d1af) - ## / 59
- mysql.workbench.6.3.10.nupkg (0a886db63d89) - ## / 61
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
MySQL Workbench 8.0.36 | 22712 | Tuesday, January 16, 2024 | Approved | |
MySQL Workbench 8.0.34 | 14304 | Friday, November 17, 2023 | Approved | |
MySQL Workbench 8.0.31 | 134265 | Tuesday, October 11, 2022 | Approved | |
MySQL Workbench 8.0.30 | 16393 | Tuesday, July 26, 2022 | Approved | |
MySQL Workbench 8.0.29 | 21253 | Tuesday, April 26, 2022 | Approved | |
MySQL Workbench 8.0.28 | 24604 | Tuesday, January 18, 2022 | Approved | |
MySQL Workbench 8.0.27 | 19586 | Tuesday, October 19, 2021 | Approved | |
MySQL Workbench 8.0.26 | 16761 | Tuesday, July 20, 2021 | Approved | |
MySQL Workbench 8.0.25 | 9007 | Tuesday, May 11, 2021 | Approved | |
MySQL Workbench 8.0.24 | 4382 | Tuesday, April 20, 2021 | Approved | |
MySQL Workbench 8.0.23 | 9438 | Monday, January 18, 2021 | Approved | |
MySQL Workbench 8.0.22 | 10090 | Monday, October 19, 2020 | Approved | |
MySQL Workbench 8.0.21 | 18021 | Monday, July 13, 2020 | Approved | |
MySQL Workbench 8.0.20 | 17866 | Monday, April 27, 2020 | Approved | |
MySQL Workbench 8.0.19 | 9357 | Monday, January 13, 2020 | Approved | |
MySQL Workbench 8.0.18 | 7404 | Monday, October 14, 2019 | Approved | |
MySQL Workbench 8.0.17 | 28649 | Monday, July 22, 2019 | Approved | |
MySQL Workbench 8.0.16 | 6579 | Thursday, April 25, 2019 | Approved | |
MySQL Workbench 8.0.15.20190204 | 4516 | Monday, February 4, 2019 | Approved | |
MySQL Workbench 8.0.14 | 1315 | Monday, January 21, 2019 | Approved | |
MySQL Workbench 8.0.13.20181109 | 3151 | Saturday, November 10, 2018 | Approved | |
MySQL Workbench 6.3.8 | 67371 | Saturday, October 22, 2016 | Approved | |
MySQL Workbench 6.3.7 | 14257 | Tuesday, June 14, 2016 | Approved | |
MySQL Workbench 6.3.6 | 19957 | Wednesday, December 16, 2015 | Approved | |
MySQL Workbench 6.3.5 | 606 | Saturday, October 24, 2015 | Approved | |
MySQL Workbench 6.3.4 | 664 | Saturday, June 20, 2015 | Approved | |
MySQL Workbench 6.2.5 | 8598 | Saturday, March 28, 2015 | Approved | |
MySQL Workbench 6.2.4 | 5099 | Friday, November 21, 2014 | Approved | |
MySQL Workbench 6.2.3 | 2083 | Friday, September 26, 2014 | Approved | |
MySQL Workbench 6.1.7 | 15187 | Sunday, June 29, 2014 | Approved | |
MySQL Workbench 6.1.6 | 6464 | Sunday, May 18, 2014 | Approved | |
MySQL Workbench 6.1.4 | 5478 | Sunday, April 6, 2014 | Approved | |
MySQL Workbench 6.0.9 | 1385 | Monday, March 31, 2014 | Approved | |
MySQL Workbench 6.0.8 | 13049 | Monday, November 18, 2013 | Approved | |
MySQL Workbench 5.2.47.1 | 3173 | Wednesday, September 11, 2013 | Approved | |
MySQL Workbench 5.2.47.0 | 933 | Monday, May 20, 2013 | Approved | |
MySQL Workbench 5.2.44.1 | 787 | Sunday, October 7, 2012 | Approved |
Ground Rules:
- This discussion is only about MySQL Workbench and the MySQL Workbench package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or MySQL Workbench, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
jivkok (maintainer) on 17 Nov 2017 10:33:44 +00:00:
User 'jivkok' (maintainer) submitted package.
chocolatey-ops (reviewer) on 17 Nov 2017 11:09:25 +00:00:
mysql.workbench has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl
, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 17 Nov 2017 11:12:06 +00:00:
mysql.workbench has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/9fcd25c6b706738a17e431bf29901d3a for details.
The package status will be changed and will be waiting on your next actions.
chocolatey-ops (reviewer) on 07 Dec 2017 11:15:07 +00:00:
We've found mysql.workbench v6.3.10 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.
chocolatey-ops (reviewer) on 22 Dec 2017 11:19:47 +00:00:
Unfortunately there has not been progress to move mysql.workbench v6.3.10 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.
Status Change - Changed status of package from 'submitted' to 'rejected'.
AdmiringWorm (reviewer) on 20 Feb 2018 20:43:27 +00:00:
Status Change - Changed status of package from 'rejected' to 'submitted'.
jivkok (maintainer) on 21 Feb 2018 01:52:13 +00:00:
User 'jivkok' (maintainer) submitted package.
jivkok (maintainer) on 21 Feb 2018 01:55:10 +00:00:
User 'jivkok' (maintainer) submitted package.
jivkok (maintainer) on 21 Feb 2018 01:58:20 +00:00:
User 'jivkok' (maintainer) submitted package.
chocolatey-ops (reviewer) on 21 Feb 2018 02:29:41 +00:00:
mysql.workbench has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl
, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 21 Feb 2018 06:39:26 +00:00:
mysql.workbench has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/e0fc575e19a74b9c34416bd892e26d95 for details.
The package status will be changed and will be waiting on your next actions.
chocolatey-ops (reviewer) on 13 Mar 2018 01:59:48 +00:00:
We've found mysql.workbench v6.3.10 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.
chocolatey-ops (reviewer) on 28 Mar 2018 02:07:22 +00:00:
Unfortunately there has not been progress to move mysql.workbench v6.3.10 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.
Status Change - Changed status of package from 'submitted' to 'rejected'.