StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4522047
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-12-23T19:59:39.800
FavoriteCount
0
LastActivityDate
2010-12-23T23:47:25.923
LastEditDate
2010-12-23T23:47:25.923
LastEditorUserId
272861
OwnerUserId
272861
ParentId
4521246
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
Your problem is well suited to a document-oriented store such as Lucene. For example you can design a schema such as Type Variety Color Origin DateSold etc : Then you can write a Lucene query such as Type:Fruit AND Color:Green. You can also build nested queries such as (Fruit:Straberry AND Color:Deep Red) AND NOT Origin:Spain. <a href="http://lucene.apache.org/" rel="nofollow">Apache Lucene</a> is a Java library with portts available for most major languages. <a href="http://lucene.apache.org/solr/" rel="nofollow">Apache Solr</a> is a full-fledged search server built using Lucene lib and easily integrable into your platform-of-choice because it has a RESTful API. BTW Solr has something called faceting which lets the user filter results using each of the criteria above. So user types fruit into search box and then gets results back. <hr> Type: - Fruit (109) - Nut (99) Origin: - Spain(32) - France(39) Color: - Red (22) - Deep Red(45) <hr> Clicking on each of the facets filters the results with the intersection. So if you want a more user-friendly interaction model, faceting/filtering is much easier, than getting users to type extensive Lucene queries. Update: You might still need to do some lexical parsing if you wish to let users type natural language queries and break it down, but given the tremendously difficult challenge, my suggestion would be to use the simple & powerful faceting approach. Hope that helps.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSearching algorithmics: Parsing and processing a request OOP style
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USMikos
UserOwnerUserId
1. USMikos
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POSearching algorithmics: Parsing and processing a request OOP style
 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.