Good evening everyone! Expect to make multiple profiles and one table
user. In profiles the majority (70-80%) of the fields are identical: last name, first name, patronymic and so on ... the number of sections planned: 2-4 pieces. Additional fields to each profile yet: 4-7 pieces. Tell me your opinion on how to do development:
- To do everything in different controllers and different tables
- Make one table with all fields and one controller
- The table pfofile to write the overlapping data, and other data to a separate table. Further, in the controller depending on the role loadable necessary models and views using the if condition{... }esle{...}
- To make a different table but in the same controller. Further, in the controller depending on the role loadable necessary models and views using the if condition{... }esle{...}
Why is it the controllers? Because you can implement all in one controller and use if, else, + scripts. Or not to split hairs and make a separate....
This will be used as a private office, and on the output in the frontend of the site. Realized that while the data coach and the data of the client. As the coach and the client will use in the bonus system. I don't know how clearly explained
Write what you want in plain Russian... In the admin part of your website has a database of trainers, clients. Each client has their contact details, subscriptions, fees, bonuses.... Each coach has the contact details of the replacement, the group which conducts, salary, bonuses,... These two roles are granted access to the personal Cabinet, where he can see information for the above listed data.
Something like that. I don't know how properly understood. Json is not likely to succeed, as this data will be requested in many places. Easier to do it through the database, than "glue" with the queries from the database. - jacquelyn_Nikolaus84 commented on June 10th 19 at 14:47