This site uses cookies. By continuing, your consent is assumed. Learn more

124.9fm shares

Dating website database schema creating


Now it is time to create the timeline for our users. Most of the time, the user wants to see posts from people they could High Five in order to elicit a conversation. Sometimes, they want to see what their competition is doing and what kind of posts are getting responses I don't think they don't want to see messages from people who are not like them and don't want to date them but I could be wrong.

We need a bunch of parameters for our method. There are the obvious ones, but we're also adding "city," "state," and "distance" so a user who is traveling can see potential dates from locations outside their typical place.

Long distance relationships are hard, but short out of town dates are not. We are also including a "competition" flag to see those posts instead. We'll make use of these later. Let's find our user and figure out what they are "man," "woman," or "it's complicated" and also get the set of what they are looking for. Now, if the location Dating website database schema creating were not passed in, we will find the user's location and get the nearby locations as well depending on their search distance.

Recent comments

If they did pass in city and state, then we'll find it and then add nearby locations. To find nearby locations we use a cypher query following the same technique we saw on the Neo4j Geospatial Queries blog post.

data model, model design, database...

We want to get posts that are either new or going backwards since a time that was passed in, but only up to when the user registered. Wait, that's not a very good idea for brand new users. We probably want to let them see past posts otherwise their feed will be empty and that's not good.

This is part 2 in...

Dating website database schema creating we don't want to run into a bug where a user in a sparse area doesn't have enough posts to reach the limit and we keep asking for relationship types going into the past forever. So we'll set a limit of say 90 days. Anything past that is probably too old to matter from a timeline perspective anyway. Now we can start getting recent posts.

We will dynamically create a relationship type for each day most likely today and then for each location find the people inside that location, and then for each one of these people get any posts from our "posted" relationship type. Now, you may be thinking Well, the reason is that most people will probably lurk.

News feed