Dating website database schema
Each have a different set of form fields that will show on their public profile pages (it's a bit like a dating website, but matches students with private tutors).The problem I have is the Agency user should be able to create multiple student/teachers.
Agencies would be a user type that had permission to create extra users (the problem here is that the created users do not need emails, usernames, passwords, reminder tokens, account activation etc).
The The next idea was to have a "profiles" table and allow users to only create 1 record in this table.
Unless they are an Agency, in which case they can create multiple.
This seems better, but something is telling me it's not right. I was wondering if anyone could point me in the right direction?
Perhaps you've worked on something similar, or just have an idea of how I could do this?
What DB tables I would need, what Models I would need etc.
Thank you :) Ok, I am doing something similar but I am not an experienced developer. But here's what I would do: Models: - Users - Agency - Teacher - Student In the Agency table I would have a field that references a user to create a one-to-one relation (user_id).
Then for the others when they are added by the Agency, all that is added is their profile info. If you need the created Teachers and Students to log in down the road, just create user entry and link them.
This way you can avoid creating unused Auth entries. Again, relatively new to laravel and MVC, take it with a grain of salt.
is defined as two hierarchies: one for textual property values, and one for the things that they describe.
This is the main hierarchy: a collection of types (or "classes"), each of which has one or more parent types.Tags: Adult Dating, affair dating, sex dating