Idea - Foreign Keys should use the same IDs, not new ones

Foreign Keys should use the same IDs, not new ones

New

Database

I noticed that the OutSystems is creating new IDs when you create a relationship between two tables:

This situation creates odd situations because the relationships are treated like new columns instead of relationships, for example:

Dropdown values coming from a Form are not being stored in the database | OutSystems

The relationship must not represent new columns because then new bugs are introduced in the applications. I wouldn't imagine performing tricky workarounds if our production DB/Excels would involve millions of records. This will slow down our development and perhaps would be more feasible to use regular software development.

MyShoppingList.oml

20 Aug 2021

Dorine Boudry

MVP

Hi Federico,

as I explained in your related post, if an attribute is already there in the child record (such as in you example {MyList}.[LocalUserId] and {MyList}.[ProductId], you establish the relationship by setting their data type to the identifier type of the entity they reference.

So there's no bug here, just a misunderstanding of how to do things.

Dorine

21 Aug 2021

Federico Navarrete

Hi Dorine, I provided you a quite detailed answer that you could read. I still consider it as an idea/bug.

21 Aug 2021

Daniël Kuhlmann

MVP

Federico, Dorine is right and you are wrong, this is not a bug, if at all just a idea, based on your misunderstanding of how one needs to define relationships in OutSystems.

21 Aug 2021