Dating website database design, primary menu
This is a very powerful system that we've developed exclusively for use by our customers. That makes MySQL have to evaluate typically all rows, as an index could be inefficient.
I'm attempting to simplify my fundraising page, and would like to show exactly how much each donation would help us out.
Это не сайт знакомств!
This topic has been dead for over six months. A general rule of thumb for making queries dating website database design, is to filter on fields that will not likely share its value with many rows. We help up and running dating sites get more profit through outsourcing and our experience.
Trusted by over 10, dating site owners.
Start your free day trial today! Which approach is better?
database design for dating site
It will most probably turn out that it performs just fine - 1 mln rows is a piece of cake for mysql. Effectively you are looking for nodes within the same proximity in a N-dimensional space, unfortunately most relational databases aren't really setup for this kind of operation I believe PostgreSQL has support for this.
Profile UserId int or guid HairColor varchar EyeColor varchar LikesMovies bit LikesHiking bit I see this a being a problem as this table could contain up to 70 columns and I think serially searching through this one gigantic table could be very slow if the user base gets large.
What I want to do is store some additional information non-searchable like favourite movie, favourite sports team etc.
Development of an intuitive navigation scheme and interface. Dating Website Development Example: It looks to me like you might already be in over your head. One thing that's unfortunate with your users table, is that you need to filter on a very non unique field with gender. Those "How would I query" questions are pretty basic. This website repository suite open-source EDA Electronic Automation tools including commencement speeches, ever.
Each of these profile questions could either contain a single value from a radio button example: Live Chat with public and private rooms. Another approach would be to identify sterotypes - i.
Create an "Responses" table that stores the choices for each 'Attribute'. Have something to contribute to this discussion?