MySQL Bugs: #37579: Save MWB Data as plain xml (not zipped)

Bug #37579	Save MWB Data as plain xml (not zipped)
Submitted:	23 Jun 2008 8:36	Modified:	19 Dec 2013 18:49
Reporter:	Lars Monecke	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Workbench	Severity:	S4 (Feature request)
Version:	5.0.22 SE	OS:	Windows (XP 64)
Assigned to:		CPU Architecture:	Any

Description:
At the moment we can add the mwb file as binary only to our development repository and need to unlock and lock the file. For us it will be much better, if we can set a project option to save mwb as plain xml file

How to repeat:
Try to add a mwb file to a subversion

Suggested fix:
Add a project option to save as plain xml file (and a new extension if needed)

Saving MWB files as plaintext for use with CVS is inappropriate because of the complex structure of the saved data. WB stores the whole GRT-Tree structure and manual merging of this data isn't possible.
We'll come up with our own solution for versioning (merging) Workbench files in a future version.

Sorry for the late reply, but it is a very important issue for us

>"Saving MWB files as plaintext for use with CVS is inappropriate because of the complex structure of the saved data"

I believe in strange of die merge algorithm of subversion. So this is a problem of your customer. 

>"We'll come up with our own solution for versioning (merging) Workbench files in a future version."

That's nice, but have no benefit for us and this is not the intention of tgis feature request.

Can you please reopen this feature request?

Okay, you are right. At the moment the xml files differs to much...