For each user there is a profile (some profile questions might be: nationality, education, age, eye color, etc, etc..).
Each of these profile questions could either contain a single value from a radio button (example: are you male or female), multiple values from a list of checkboxes (example: check your hobbies and interests) or text (ex: tell in a short paragraph what you are looking for).
When I heard the advert for Hello You on Heart I thought well, one more try maybe this one would be different.
After a couple of weeks this guy’s profile showed up.
Don't sabotage your chances of happiness by digitally stalking a potential new partner.
I want to share a story about what I call "dating site stalking." This term applies to someone who consistently and obsessively checks the profile of a person they've met and begun dating. It seems simple enough: to check up on the person they're now dating and communicating with on an ongoing basis.
He is amazing and I am so in love and he is in love with me too.Does anyone have any advice as to the best way to design this.Here are some of the options I am considering: 1) Create a different table for each profile question: example: Eye Color -------- User Id (int or guid) Eye Color (varchar) Interests --------- User Id Interest Value I see this as being a problem because there could be upwards of 50 table joins for each search query and the database would need to be updated if a profile question is added or no longer used.We like all the same things, finish each other’s sentences, want the same things and have already accepted that we are going to spend our life together!I had to let you know as I want to give people out there hope, keep looking and hold on, don’t settle and wait for your prince.