Reverse engineering creates duplicated foreign keys

Question

Reverse engineering creates duplicated foreign keys

Opened this issue 6 years ago · 3 comments

Answer 1 · 2018-07-26T13:28:05.000Z

Would you provide a more detailed description with an example?

Answer 2 · 2018-07-26T14:03:52.000Z

When reverse engineering a table definition from an existing table, the foreign key will be duplicated. For example, when reverse engineering a table called SessionTask, the automatic definition is:
%{
-> experiment.Session
-> experiment.Session
-> experiment.TaskProtocol
-> experiment.TaskProtocol
%}

Answer 3 · 2018-07-26T14:09:22.000Z

I have never seen this before and the reverse engineer feature has been there for several years. Let's reproduce and trace it down.