Hi All I Am designing a Dating Website , where im using tables named : 1. 'users' :- To save basic info like username,password,email-ID ,first name, last name . 2. 'profiles' :- To save other attributes like height,weight etc. 3.'searches' :- user can have multiple search and save his every search(table has id and other searched Criteria according to which he will be notified periodically of his matches. 4. 'relationship':- if a user declares a relationship with other user , and other person accepts it. it will be saved in this table with fields as 'id', 'suitor_id', 'interest_id' (suitor id and interest id will be foreign keys from users table and will enjoy special privileged features in the relation which they normally cant have with other users. User can have multiple relationships.
I have set hasone association in users model for profile model. and hasmany for searches But am confused about relation : HABTM or Join model. Further i want to have one more table called 'searchable', in which a user can set values for particular attributes(in a form with layout almost same as that of search form) . where he can hide himself from public view and set that person with those particular attributes can only search him, other wise he will not be searchable to others. and that particular person too can only see those attributes of the searched user profile which the searched user set to be visible(which can be seleacted by a check box next to the attributes label in the form). . was wondering how to implement this pragmatically , though i have thought about number of ways , i want to implement somthing that it could deal with performance for at least 100k+ users. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
