All we need is an easy explanation of the problem, so here it is.
I’m building a database for a real estate company.
The real estate properties are managed by sales people using a CodeIgniter website.
How should I proceed with the database design for this table? Fields such as
price etc., are pretty straightforward, however there are some sections like
Kitchen Appliances, ‘Property Usage’ etc., where the sales people can check multiple values for each field.
Furthermore, a property can have multiple people attached to it from the table
people, such as
property lawyer, etc. Should I use one field for these people or create another table and normalize the bindings?
Is the best way to proceed just using one field and using serialized data or is there a better way for this?
How to solve :
I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.
You can keep one table for property and one master table for roles and them assign that role to a user in the user table and can keep one to many association between property and users by having separate table property_users
Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂