Bug #50054 Allow projects files to work in 'unzipped' state
Submitted: 4 Jan 2010 14:50 Modified: 19 Jul 2010 10:43
Reporter: Craig Fowler Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S4 (Feature request)
Version:5.2.10 OS:Any
Assigned to: CPU Architecture:Any
Tags: file, mwb, project, version-control

[4 Jan 2010 14:50] Craig Fowler
Description:
Following up a brief discussion on IRC a while back, could I request that Workbench is able to work with (save and open) .mwb projects in an 'unzipped' state.

Workbench projects are primarily an XML file (plus one or more SQLlite database files and possibly other supporting files in the future), compressed into a single zip file with the extension .mwb.

It would be nice if WB could open/save projects in this file format or as an unzipped 'project directory' (containing the files in a single directory structure, otherwise the same as they would have been in the zip file).

The main use-case I am thinking of here is that unzipped projects are more version-control friendly.  My VCS of choice will then be able to treat the main project XML file (at least) as text, rather than seeing the whole .mwb project file as an opaque binary.

I understand that an old version of WB unofficially supported this feature but since new functionality was added in a more recent version it was discarded.

How to repeat:
N/A - feature request
[5 Jan 2010 11:27] Susanne Ebrecht
Many thanks for writing a feature request.
[19 Jul 2010 10:43] Craig Fowler
I had a discussion with akojima about this.  Actually, I really don't care about this so much anymore.

Yes, unzipped project files means that I can put them in version control but then - "so what".  I can't think of anything cool that I could actually do with a MWB project in version control.