Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with database-design
Search options not deleted
user 289612
For questions about structuring the data within a database. How to lay out tables, whether to use a relational DB or not, etc.
2
votes
1
answer
140
views
Architectural considerations for frequently matching similar users
I've been trying to design a backend architecture to a SPA that satisfies the following:
user constantly answer yes/no questions (ex: tinder swipe cards)
The application calculates each user's simil …
- 131