Book a Demo

Author Topic: "Get All Latest" is potentialy dangerous  (Read 12214 times)

shimon

  • EA User
  • **
  • Posts: 172
  • Karma: +6/-0
    • View Profile
Re: "Get All Latest" is potentialy dangerous
« Reply #15 on: July 15, 2014, 05:49:39 pm »
Hi tis,
Did you report this issue to Sparx?
Can you describe when this happens?


tjs

  • EA Novice
  • *
  • Posts: 19
  • Karma: +0/-0
    • View Profile
Re: "Get All Latest" is potentialy dangerous
« Reply #16 on: July 15, 2014, 11:44:16 pm »
My posts started @ "Re: "Get All Latest" is potentialy dangerous
Reply #5" and yes I reported the issue.

When a user clicks "Get All Latest" in v11, while in a centralized team configuration (EA v11 + SQL DBMS + SVN).. links get broken.  To restore the links,  I've had to "check out" and then "undo check out" on packages with missing content.  Similarly importing the latest revision of a problem package from XMI also restores the link, but this also has been found to cause collatteral damage, breaking links to other packages (seperate but related issue).    

It seems to me that problems arise with the synchronization between XMI imported data and DBMS data if the entire model isn't imported all at once.   From what I read, "Get All latest" only updates the packages that have changed and that aren't locked.

shimon

  • EA User
  • **
  • Posts: 172
  • Karma: +6/-0
    • View Profile
Re: "Get All Latest" is potentialy dangerous
« Reply #17 on: July 17, 2014, 10:13:15 pm »
Did you try building a local.eap file that mirrors the DB centric model?
I mean creating a new eap and linking it to model branches that are built from the central DBMS based model.

tjs

  • EA Novice
  • *
  • Posts: 19
  • Karma: +0/-0
    • View Profile
Re: "Get All Latest" is potentialy dangerous
« Reply #18 on: July 18, 2014, 12:40:49 am »
Can you clarify?  I did create a local.eap importing .xmi files to reconstitute  the model that we had in the DBMS.  I did not attempt to connect those imported branches to version control (SVN).

In attempt to fix the "get all latest" issue, the DB became corrupted.  We ended up dropping all the tables in the DB, reloading the schema and reimporting the model (form the revisioned XML).  We did not re-connect SVN, all members of our team are currently working from DB model w/out revisioning.