是否可以将MySQL Workbench文件另存为纯XML? [英] Is it possible to save MySQL Workbench files as plain XML?

问题描述

DB Designer有很多错误，但是一个突出的功能是数据库模型默认情况下以纯XML保存.

DB Designer had a lot of bugs but one outstanding feature was that database models were saved in plain XML by default.

这使用户可以通过SVN或超越比较" 差异文件版本，轻松找到对数据库所做的任何更改.

This allowed a user to diff file versions via SVN or Beyond Compare, easily finding any changes made to the database.

不幸的是，DB Designer的继承人MySQL Workbench以专有MVW文件格式存储文件，该格式不可读.

Unfortunately, DB Designer's succsssor, MySQL Workbench, stores files in a proprietary MVW file format, which is unreadable.

是否可以强制将MySQL Workbench保存为XML?

推荐答案

否，当前版本(5.2.10 beta)不支持.

No, the current version (5.2.10 beta) does not support that.

但是，文件格式不是专有的-它是一个简单的zip存档.它包含一个XML文档，它是完整的数据库模型.几个月前，我写了这个SO问题，其目标与您相同似乎有.我希望能够做到svn diff model.mwb

However, the file format is not proprietary - its a simple zip archive. It contains a single XML document which is the complete database model. I wrote this SO question a couple of months ago with the same goal as you seem to have. I wanted to be able to do svn diff model.mwb

我到达那里的答案帮助我编写了一个小脚本，该脚本先将文件解压缩，然后再将其传递给diff工具.它工作得很好，如果您有兴趣，我可以将它发布在某个地方.

The answer I got there helped me write a small script which unzipped the file before passing it to the diff tool. It worked decently and if you're interested I can post it somewhere.

我最近也在Workbench论坛上启动了线程关于此问题.希望开发团队中的某人可以对此提供更多的投入.

I also very recently started a thread on the Workbench forum about this issue. Hopefully someone on the development team can provide some more input on this.

MySQL Bug#51203 正在跟踪它目标为6.0.

it is now being tracked by MySQL Bug #51203 with a target of 6.0.

这篇关于是否可以将MySQL Workbench文件另存为纯XML?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！