Thanks for your reply!
From the UI I’m getting it, could you suggest me with any example form the Java OOP or Database side?
Should I create an abstract class end extend objects for all my parameters types?
So for the main entity :
- there is a parameter named “point”
- this parameter can be of different types that the user can select from drop down menu
- types can be a foreign key of an other entity (lookup drop down menu), any other object, string or int
- only one value type can be stored(so it’s an OR) into the database
It’s similar to the car example :
if you select one brand then the second dropdown will allow you to select the sub-brand options, the only difference here is that, if from the lookup dropdown menu there is no option, then the user can free text the value manually of the id.
…at the end in the database I want only to store 2 columns corresponding to my “point” param.
2 columns :
typePoint: corresponds to my different objects, defined in an enum
pointValue : is the object value of type as defined in typePoint (EntityA, EntityB, EntityC, EntityD or EntityE)
Just want to avoid to have many columns in my database, since I use only one of 5 total…
What would be the best solution ? Do you have any example about this?