Book a Demo

Author Topic: 854: Cross-DB technology transport issues  (Read 3355 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
854: Cross-DB technology transport issues
« on: April 15, 2010, 12:14:54 am »
If you create a new project from the EAExample.eap to an .EAP file and then transfer it up to a SQL Server using project transfer.  I, for one, would expect the XMI export from both repositories to be identical - after all even the object ids are (should be) the same!

They aren't identical.  Could someone (Sparxian) as a matter of urgency explain what's going on here?

Given that EA even after a number of years of requests can't even produce the same output twice in a row (and therefore direct comparison with comparators like Beyond Compare is frustrated), sorting the generated output shows SUBSTANTIVE differences.


Steps:
Create a new project (EANew) from EAExample.  Export project to XMI.  Transfer project to SQL Server (created using Sparx supplied SQL File).  Export project to XMI.

Compare the two XMIs - observe the substantive differences:
Additional entires in one and not the other
Various IDs different in one from the other


Reported and sample XMI's sent to Sparx

I don't know how long this has been going on - I'm only testing with 854.  Actually, I had problems re-importing packages I'd just exported.  If you do any XMI import/export you may care to perform the same experiment with your own setup.  By using the EAExample DB, we DO Provide a standardized test.

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!