Back
Issue with relations on database
I'm creating a food ordering website for businesses.
I'm having issues with the relations on my database
I attached the attributes for the collections I'm having issues with. I've mostly worked with non relational databases like mongo but I believe I'm using the correct "standards" for this kind of database (correct me if I'm wrong)
APP CONTEXT/ BACKGROUND
- Each user can be either be a System Admin, Restaurant, Business, or Worker
- When I want to grab the Restaurant from a user I just get the logged user and travel through its contents made by the relations to get the Restaurant it owns and then get the orders of that restaurant. (Maybe this is a bad practice idk)
- When I try and display that info on the console I'm not getting the Restaurant the order belongs to and neither the Business that made the order, even though they are on my attributes and my schema
Attached the result of my console log at the end
TL;DR
Developers are debating whether to store only the Business and Restaurant names in the order for a food ordering website. They are facing issues with relations in the database. They included attributes for the collections but are struggling to fetch the desired information about the Restaurant and Business linked to the orders. A suggested solution could be to review the database schema and data retrieval methods to ensure proper association and retrieval of Restaurant and Business information. Is it ok for me to just store the Business and Restaurant name in the order or is that bad in the long term?
