I'm sorry, I can't edit my post (won't save). Here are two links which show my structure explained above:
In 95% of cases in SQL DBs it's good to introduce an artificial "id" (integer sequence) primary key even if some subset of your fields is unique. It's far better for data handling - as you probably noticed ;).
You have mentioned your "laziness" - I'd say - refactor the data structure, because your problems may only stack up in the future.
Thanks for the tip!
szegad said:
You have mentioned your "laziness" - I'd say - refactor the data structure, because your problems may only stack up in the future.
Yeah, I plan to do that. But I think I need some more learning. As I said, I struggle with creating a useful and logic structur for my purpose
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community