Author Topic: ForeignKey Relationships & DDL Reverse Enginee (Read 11626 times)

mogarick · « **on:** October 13, 2003, 02:25:16 am »

Hi,
I'm having problems with the DDL Reverse Engineer option of EA.

The problem arrises when a table has more than one Foreign key. The Table shows all the foreign keys, BUT EA only creates a relationship just for the first Foreign Key in the table.

I´m using MySQL with ODBC Driver 3.51.
ERWin has no problems in reverse engineer the same DB with the Same ODBC driver.

Is it an EA BUG?

Please Help me

hd · « **Reply #1 on:** October 13, 2003, 03:06:57 pm »

It is a bug in EA

, and we are currently working on a solution to the problem.

ola_strandberg · « **Reply #2 on:** October 16, 2003, 09:02:01 am »

This is causing me a lot of grief as well, but reverse engineering from Oracle.

In addition, synchronizing changes in a table picks up that there are new foreign keys and creates the stereotyped method, but it doesn't create the association to the referenced class.

Work harder

Best regards,
Ola

mogarick · « **Reply #3 on:** October 24, 2003, 08:32:06 pm »

Hi,
it´s me again.

i'd just like to know when are you planning to solve this foreign key bug.

as i have seen the 2 last revision history (648 and 649) and i haven't seen this fix yet

Greetings and congratulations for your product.

hd · « **Reply #4 on:** October 26, 2003, 01:18:35 pm »

Improvements to foreign key creation/generation are currently being tested, and it is hoped to be ready for the next release (build 650).

mogarick · « **Reply #5 on:** October 27, 2003, 10:07:48 pm »

well, build 650 has been released but looking for the change I got disapointed

I hope the next release fix this long waited (at least, speaking just for myself) bug

Greetings

hd · « **Reply #6 on:** October 28, 2003, 01:16:11 pm »

Sorry - it wasn't quite ready for release with build 650

ola_strandberg · « **Reply #7 on:** November 05, 2003, 02:34:11 am »

Guys,
can you please provide an update of the actual status of this

I find myself checking for new builds every day, with hopes going up with each new build and then disappointment when this hasn't been fixed while new functionality is still being introduced

Regards,
Ola (build 644 user, upgraded to 648)

allegatok · « **Reply #8 on:** November 05, 2003, 03:00:18 am »

Hmm.... I posted a message fw days ago about foreign key management
but didn't receive an answer. May be it was poorly explained or they are just working on it. My current feeling is that the 'data modeling feature' needs much more than a quick fix and I would like to know if there is any current plan to
'upgrade' it as to speak. It's kind of awkward to work with it. Hope the next build solve all the problems.
Mario
:-/

CJ · « **Reply #9 on:** November 05, 2003, 04:57:08 am »

G'day folks,

I'm using EA 649 to reverse engineer (and generate DDL for) our Oracle database.

I have noticed once that one of our tables was missing a foreign key. I synchronized the model with the database (took a while ... big database), and that brought in the missing foreign key.

Over all, the rest of the model looks fine. Have you tried synchronizing your model (maybe a backup copy to not mess up any current work you may have done in your project file)?

No a put down on EA (or any of your ligit concerns) by any means, but I never trust the results of any tool 100%(because of bugs, my own mistakes, some kind of burp on the database/network/workstation ...) For any part of the reverse-engineered model I work with, I like to verify it's correctness with a direct query from the database. (Maybe a mild paranoia???)

ola_strandberg · « **Reply #10 on:** November 05, 2003, 06:19:25 am »

Hi Jason,

I have some good news and some bad news:
The good news is that you are right - it works.
The bad news is that I am also right - Please see my new post "New DDL problems: was Foreign key relationships..."

Again, I apologize for not investigating my problem further and just assuming that it was the same as the above. (On the other hand, I didn't want to report a "bug" and told to RTFM)

Cheers,
Ola

mogarick · « **Reply #11 on:** November 06, 2003, 10:13:47 am »

Hi,
The problems seems to persist in the new build 651.
I syncronized the tables but the problems is there yet.
The problem is not the FK recognition, but the respective FK relationships. I mean the table shows there are FK on it, but it just draw the First FK relationship. It doesn't draw the other FK relationships the table has too.

I received an answer from EA team telling me the problem was gonna be fixed for build 650, but 651 is out and the problem is still present.

I'd like to know which build will fix this bug

Greetings
Ricardo Montoya

Gaz · « **Reply #12 on:** November 13, 2003, 04:28:21 pm »

Just started using EA, initially for data modelling, but intention to extend into full object modelling.

Have the same problem, and it appears to be related to the length of the FK constraint name. More than 30 something characters, and things go funny.

ola_strandberg · « **Reply #13 on:** November 20, 2003, 02:15:21 am »

If you are suffering from this problem - DO NOT UPGRADE to build 653!

New bug no 1:
All the requirements associated with the tables are cleared when synchronizing (I have lost 1000's of associations...)

New bug no 2:
When synchronizing and not including all associated tables, the following error message appears before EA crashes - "DAO.Recordset [3315] Field 't_connector.DestRole' can't be a zero-length string"

I am just so glad the we version control and backup our models...

I have reported this to sparx support.

/O

CJ · « **Reply #14 on:** November 21, 2003, 05:07:35 am »

I'd say anyone who doesn't back up their EA projects before upgrades, and doesn't back up once in a while in addition to that, should really learn to be a little more paranoid.

Ola, thanks for the heads up. If you wouldn't mind, since you've really been on top of this, would you mind replying to this thread when a future build is up to snuff? Much appreciated.

Sparx Systems Forum

News: