StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18100143
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
6
CommunityOwnedDate
CreationDate
2013-08-07T09:49:17.430
FavoriteCount
0
LastActivityDate
2013-08-07T09:49:17.430
LastEditDate
LastEditorUserId
0
OwnerUserId
2527433
ParentId
18084408
PostTypeId
2
Score
44
ViewCount
0
LastEditorDisplayName
text
Body
Since no one made any answer, I will go ahead with my suggestion then. I think the best fit for your big database is using <code>remote</code> with <code>typeahead.js</code>. Quick example: <pre><code>$('#user-search').typeahead({ name: 'user-search', remote: '/search.php?query=%QUERY' // you can change anything but %QUERY }); </code></pre> What it does is when you type characters in the <code>input#user-search</code> it will send AJAX request to the page <code>search.php</code> with query as the content of the input. On <code>search.php</code> you can catch this query and look it up in your DB: <pre><code>$query = $_GET['query'].'%'; // add % for LIKE query later // do query $stmt = $dbh->prepare('SELECT username FROM users WHERE username LIKE = :query'); $stmt->bindParam(':query', $query, PDO::PARAM_STR); $stmt->execute(); // populate results $results = array(); foreach ($stmt->fetchAll(PDO::FETCH_COLUMN) as $row) { $results[] = $row; } // and return to typeahead return json_encode($results); </code></pre> Of course since your DB is quite big, you should optimize your SQL query to query faster, maybe cache the result, etc. On the typeahead side, to reduce load to query DB, you can specify <code>minLength</code> or <code>limit</code>: <pre><code>$('#user-search').typeahead({ name: 'user-search', remote: '/search.php?query=%QUERY', minLength: 3, // send AJAX request only after user type in at least 3 characters limit: 10 // limit to show only 10 results }); </code></pre> So it doesn't really matter how big your DB is, this approach should work nicely. This is an example in PHP but of course it should be the same for whatever backend you have. Hope you get the basic idea.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to use typeahead.js with a large database
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USHieu Nguyen
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to use typeahead.js with a large database
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.