Structure of database

Good day ))
Please advise on below.
All Users have 1 or more professions. Each proffesion has condition out of 3 options: verified, pending, unverified. Change of this data is not frequent. Please advise good structure of database for WU and future development.

Hey

For the professions, are you going to allow the user to type the profession, or are you going to have some predefined ones? If they are predefined, I recommend you use Option Sets, if not, create it as a data type. Regarding the profession condition, I would 100% use option sets and add it as a field in the profession data type or option set (depending on what I said in the first sentence)

Hope this helps you

Julian

I have predefined list of professions but some users might have unique proffesions.

Then create it as a data type but still use an Option Set to allow them to choose a predefined option

1 Like

@valerijs.melikovs def dont follow that. There’s no reason to use option sets when ur using a dataset. Just load the predefined list as options and allow a user to add anew one as well.

1 Like

How are you then suposed to load a predefined list if you are not using Option Sets for it?

Predefined list as “data type DtRank”

The only problem with that is that would have to create a “small sistem” to create this DtRanks, however, with option sets, it is much easier and you are still just using it to display the name.

What problems coming with small system?

That you have to set up the system, however, with the option sets, you can just click on add a new option and do nothing else

Is it possible that user add option in option set?

Hey, no

1 Like

that doesnt make any sense. its the opposite of customizable and has no benefit as it’s being stored within a dataset anyways. There’s no system needed to store the values other than a DB I guess.