Data Model - bug on saving the diagram

[lnfloyd]

Good evening.

First of all, sorry by bad english - I'm from Brazil and, currently, I have a bad pratice in this language.

I have a data model in EA 7.5, since I've using the trial version.

Important: My company bought one license (enterprise/floating) and we already have started to use it.

In my data model, I have some diagrams, each diagram, have many tables and their relationships. There is one relationship between these tables that presents me a bug. All tables have the <database> attribute set to Oracle.

So, let's go to the bugs description.

First, I verified that the relationship isn't a an FK, in fact. So, I deleted it and recreated. No bugs here...

After, that I turned it into a FK (right button click over the assossiation, left click in Foreign Keys option in the popup menu, select the datafields of both tables and, then, click on the ok button). No bugs yet.

No further changes in all diagram or in the Enterprise Architect Project file.

When I try to save the diagram, the bug is unveiled: the FK I’ve just created disappears - only the assossiation persists, but the operation related to that FK, the label that is presented at the left side, close to the datafield name on the table, an the label that shows which datafield of the source table is equals of the datafield of the destination table (both of this stuffs) disappears completely.

I'd try four different ways to save the changes:
1- keyboard shortcut - ctrl + s;
2- clicked the save icon (there are two*, but I waited to the tooltip to assure I'm clicking on the right button);
3- overwriting the current file through save as option - presente on menu file; and
4- created a copy of such file using the same option of as item #3.

*PS: that's one mor issue... undo and save buttons have the same icon...

Please, solve it and warn all users that has support of the Spark Systems to obtain the version that contains this and another fixes.


Thanks a lot!

[lubos]

We have the same experience.
This is quite a old bug, but still not resolved.
The behavior is completely undeterministic, the same steps are OK one time and cause a bug you described (losing method) second time.
We have not found out any steps order that will succeed always.

[olivier028]

*PS: that's one mor issue... undo and save buttons have the same icon...

I have been able to solve this issue by resetting the toolbar.

You can do this by clicking on the little triangle on the right of the toolbaar and select 'Add or Remove Buttons' -> 'Default Tools' and press 'Reset Toolbar' below. This solved my issue with the icons.

Hope it helps.

Cheers, Olivier

[lweath]

Still a problem 8 years later in 13.5.

Working on a saved diagram, deleting and recreating the association in between the tables, with no other changes, causes the diagram to be flagged as needing saved. Trying to close the diagram without saving still results in the FK constraint being deleted. The diagram still shows the correct association link in between the tables with all of the correct labels, but without the constraint in place.

[Paolo F Cantoni]

Still a problem 8 years later in 13.5.

Working on a saved diagram, deleting and recreating the association in between the tables, with no other changes, causes the diagram to be flagged as needing saved. Trying to close the diagram without saving still results in the FK constraint being deleted. The diagram still shows the correct association link in between the tables with all of the correct labels, but without the constraint in place.

Hi lweath,

I'm not sure it's a bug (in Sparx's view).  As part of standard diagram processing, if you don't a diagram on closing with a NEW vertex or arc, EA assumes that you didn't want them and will purge them from the model.

In your case deleting (I assume yo9u mean purging from the model - not just hiding on the diagram) and creating the NEW arc will "dirty" the diagram.  Thus, it needs to be saved.  In the case of a Foreign Key Constraint, the issue is more complicated because you (effectively) have a two-step process.  Have you confirmed that saving the "dirty" diagram correctly saves the FK Constraint?

I have some sympathy for Sparx's view but the EAUI could have been better framed to alert users to what may happen.

Paolo

[lweath]

For me, the fix ended up being saving in between every diagram change. I had been queuing up a deletion of the association and then recreating the association with the correct FK constraint. When saving the diagram, the displayed association (including all the labels) were correct, but the FK constraint from the table was deleted. If I changed my process and deleted the association, saved the diagram and then recreated the association, everything was saved correctly.

I had contacted support on this and the other suggestion they had was using db builder, which I had not used. Will try that in the future.