Efml Associations - Repeat Bug
Posted: Mon 02 May 2022 13:18
Version: 6.12.1419
I detected a problem, to occur was like this:
I have a table A that has two fields that reference table B.
But by mistake I created the two references in table A for the same field that is
FK_TableA_TableB (TableBId = TableBId)
FK_TableA_TableB_Another (TableBId = TableBId)
I updated the model by the database and it created the two references, so far so good. But I think it should alert for two references to the same fields, duplicating the property.
But the problem is when I make the correction:
FK_TableA_TableB (TableBId = TableBId)
FK_TableA_TableB_Another (TableBId_Another = TableBId)
When updating the model by the database it created the reference as it should but did not remove the reference that was duplicated.
So in the model it was 3, and in the database there are two.
Another thing as a suggestion would be the name of the associations to be the name of the FK, which is much easier to find.
I detected a problem, to occur was like this:
I have a table A that has two fields that reference table B.
But by mistake I created the two references in table A for the same field that is
FK_TableA_TableB (TableBId = TableBId)
FK_TableA_TableB_Another (TableBId = TableBId)
I updated the model by the database and it created the two references, so far so good. But I think it should alert for two references to the same fields, duplicating the property.
But the problem is when I make the correction:
FK_TableA_TableB (TableBId = TableBId)
FK_TableA_TableB_Another (TableBId_Another = TableBId)
When updating the model by the database it created the reference as it should but did not remove the reference that was duplicated.
So in the model it was 3, and in the database there are two.
Another thing as a suggestion would be the name of the associations to be the name of the FK, which is much easier to find.