1
Suggestions and Requests / Is it any easier to resolve replication conflicts?
« on: June 13, 2011, 10:25:15 am »
As I have reported several times in the Bugs forum over the last couple of years, since sometime back in the version 7.1 days, I find it virtually impossible to intelligently resolve conflicts when merging a replica back into the design master.
I go to Resolve Synchronization Errors and look in Table with Conflicts and Conflicting Records and Conflict Details, and I see some cryptic stuff that is impossible to understand if one isn't a database expert (and even then, perhaps impossible to understand).
I have gotten many suggestions from people on the forum here, particularly Geert, and they have been very helpful and have helped us to the point where these constant replication conflicts are a serious inconvenience but not really a major calamity like they were. Mostly, we re-sync to the design master often, so most of the time we get no conflicts and when we do, it's a dozen or two at most and not several dozen to a hundred or more like we got back in the beginning.
We have completely given up on being able to implicitly trust the database anyway, and so we are validating the output of the tool rather than the tool itself... we maintain a reference set of source files and then whenever we export source from the model, we do a diff to make sure nothing changed in the generated code.
But, I digress...
My question is, EA draws diagrams based on the contents of the EAP database. So, is it not possible for EA to read a conflicted database, draw in black those parts that are not conflicted, and draw in blue (for the original) and red (for the replica) those parts that are conflicted? Then I could just go through and look for reds and blues on my diagram, and in each case delete the ones I don't want and save the others. That would be a breeze, would completely and forever solve the problem, and this whole issue would go away almost immediately.
I am (still) using version 7.5.850 and we are unable to upgrade until this phase of the project is over (for many reasons including that this is now the devil we know), and I did ask for this almost two years ago, so is this or anything like it something that's available in version 8 or 9? If not that, then is it at least easier in version 8 or 9 to figure out where the conflicts are and determine how to resolve them?
Thanks...
I go to Resolve Synchronization Errors and look in Table with Conflicts and Conflicting Records and Conflict Details, and I see some cryptic stuff that is impossible to understand if one isn't a database expert (and even then, perhaps impossible to understand).
I have gotten many suggestions from people on the forum here, particularly Geert, and they have been very helpful and have helped us to the point where these constant replication conflicts are a serious inconvenience but not really a major calamity like they were. Mostly, we re-sync to the design master often, so most of the time we get no conflicts and when we do, it's a dozen or two at most and not several dozen to a hundred or more like we got back in the beginning.
We have completely given up on being able to implicitly trust the database anyway, and so we are validating the output of the tool rather than the tool itself... we maintain a reference set of source files and then whenever we export source from the model, we do a diff to make sure nothing changed in the generated code.
But, I digress...
My question is, EA draws diagrams based on the contents of the EAP database. So, is it not possible for EA to read a conflicted database, draw in black those parts that are not conflicted, and draw in blue (for the original) and red (for the replica) those parts that are conflicted? Then I could just go through and look for reds and blues on my diagram, and in each case delete the ones I don't want and save the others. That would be a breeze, would completely and forever solve the problem, and this whole issue would go away almost immediately.
I am (still) using version 7.5.850 and we are unable to upgrade until this phase of the project is over (for many reasons including that this is now the devil we know), and I did ask for this almost two years ago, so is this or anything like it something that's available in version 8 or 9? If not that, then is it at least easier in version 8 or 9 to figure out where the conflicts are and determine how to resolve them?
Thanks...