Possible bug in Foreign key relationships

[cojmh]

Hi

I have been playing around with EA and the UML documentation for a project that I am doing, and have been very impressed so far with EA.

However I have come across something that I can only see as a bug, because when I need to make a change sometimes the change goes through fine and othertimes it goes wrong.

The problem I am having is that I have several oracle tables designed within EA. However I needed to go back and standardised some of the names by changing upper case letters to lower case letters. Once I had done this, most of the foreign keys went wrong, but some remained ok.

As a side note, I am also experiencing problems with the generation of constraints, but only since I changed a couple of the letters from upper to lower case ( as described in this post: http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.cgi?board=general;action=display;num=1094582304;start=1#1)

I am using 4.1.736 - How do I go back to 7.1.734 and convert the .EAP file?

Any help would be appreciated.

Jonathan

[thomaskilian]

Jonathan,
you can go back to an earlier release if you replace your EA.EXE by the appropriate release. I can send you that release if you didn't keep it. (N.B.: you meant 4.1.734, didn't you?)

If you stay in the major release the database must not be converted.  (There is no downgrade tool to go from 4.0 to 3.6 exept via XML)

[cojmh]

thomas,

If you could send me that .exe file, I'll give it ago. How do you want to send the file to me?

Thanks,

Jonathan

[thomaskilian]

Drop me your mail address via private member message. I'll send you the zipped exe (3,5 MB still)

[cojmh]

I have tried build 734 and I still have the problem.

So I have contacted sparx about this and asked when it would be resolved.

They have told me that they know about the bug and that it will be sorted in build 738 (next release), just incase anyone wanted to know.

Jonathan

[beaf]

I must admit, I had a similar problem, but in reverse. I changed table names to uppercase, but the constraints all stayed in lower case. In particular the primary key was the most frustrating as retaining a naming convention helps to keep some of the semantics of the model in the naming. Would be handy if looking at the next version as to whether constraint names which are created based on the table name or column name could be automatically updated.

Would still like to say how impressive the EA features are in this area (and how stable it is). It is so nice to be pernickity (sorry, know how this can be annoying) rather than just wishing the basics would work properly (like ERWin - that doesn't model very well and its designed specifically for this purpose)!