🗃️ add database layout for IFOPT

[MrKrisKrisu]

see #2411

[jeyemwey]

Why is it necessary to have 5 fields in the database for this? IMO it would be sufficient to keep it in one column with : in between.

[HerrLevin]

@jeyemwey It's not necessary per say, but you can leverage the relational characteristics of the individual segments. That way, we can group stations based on segment a, b and c to use another API or stuff like that. Doing that with LIKE will be way less efficient.

[jeyemwey]

you can leverage the relational characteristics of the individual segments. That way, we can group stations based on segment a, b and c to use another API or stuff like that. Doing that with LIKE will be way less efficient.

Jetzt wo ich drüber nachdenke, kann ich die Chancen sehen. Allein die Chance, Country-Informationen darzustellen, und zwar abseits von Ziffern in einer IBNR, ist ja schon nice. :3

[MrKrisKrisu]

It's not necessary per say

In the context of database normalization, I would argue that this is the most sensible approach. Since each attribute provides its own context, it is also easier to select - and I also see improved performance if we later want to search by country or municipal unit, for example.