Bug #35645 | Multi Database version support | ||
---|---|---|---|
Submitted: | 28 Mar 2008 13:53 | Modified: | 14 Jan 2009 15:18 |
Reporter: | Chris Crossley | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Workbench | Severity: | S4 (Feature request) |
Version: | 5.0.16 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[28 Mar 2008 13:53]
Chris Crossley
[31 Mar 2008 17:54]
Valeriy Kravchuk
Please, be more specific. What exactly do you want Workbench to support for 5.0 vs. 5.1? What's wrond with generating code for 5.0.x and assuming it will still be supported by newer versions, 5.1 and/or 6.0?
[31 Mar 2008 21:09]
Chris Crossley
My issue is backward compatability. For example if i have live on 5.0 and your script generates a 5.1 specific bit of code. Then i can't apply it. It would also not be unusual to have a 4.x in a live setup. Waiting an upgrade with current development taking place. Hence a 5.1 script would fall foul as well. One would only need the last patch of every major release covered and in my case all my DB are 5.0 and about.
[14 Jan 2009 15:18]
Susanne Ebrecht
MySQL Workbench mainly is developed for MySQL server 5.1 and higher. We won't support lower server version then 5.1. We will fix security issue also for 5.0 but nothing more. Main server for Workbench at the moment is 5.1.