Images to explain better the context:
This image shows the registration form, in this case the registration type general has only 1 custom question associated (Phone), so this question will appear twice because it was selected "2" for the registration type "general": https://ibb.co/f3Y3vz
This image shows how the database should stay based on the registration form image above: https://ibb.co/jXgTTK
One thing will have numerous labels. Also, one tag will have a place with numerous things. This infers to me that you'll perhaps require a delegate table to conquer the many-to-numerous deterrent.
Something like:
Table: Items
Columns: Item_ID, Item_Title, Content
Table: Tags
Columns: Tag_ID, Tag_Title
Table: Items_Tags
Columns: Item_ID, Tag_ID
It may be that your web application is madly prominent and require denormalising not far off, however it's futile muddying the waters too soon.
By:Xtreem Solution
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community