Search code examples
xmlerwin

Export erwin to xml - caveats


We're using Erwin 7.x to model our database. The process becomes very painful when we need to work on multiple versions of it - erwin format is binary and not automatically mergeable.

So, what I did is I exported the model to an XML file, cleaned it using XSLT. It all looked good till I found a problem with relationships - historically, we do not name our relationships and leave that to erwin, so the names are R_1, R_2, and so on. After opening an XML erwin starts producing duplicate relationship names.

The solution is to assign names ourselves which is fine and should have been done in the first place. The problem now is that we don't have any trust that there won't be more caveats later.

Now to the question: has anybody tried working with erwin through XML exclusively for a considerable amount of time?


Solution

  • I have been using XML approach for a year now and found no issues. I just need to give unique names to new relationships.

    We are not going to upgrade ERWIN for that project so there is no a time bomb here.