StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1035043
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-06-23T20:38:59.547
FavoriteCount
0
LastActivityDate
2009-06-24T05:33:25.243
LastEditDate
2009-06-24T05:33:25.243
LastEditorUserId
1702
OwnerUserId
1702
ParentId
1030887
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
<p>Basically, you have two types of search parameters: textual and spatial. You can probably use one type to filter the results you got from the other. For example, for someone looking for a .NET developer job near Atlanta, GA you could either first retrieve all the .NET developer jobs and filter for location, or retrieve all jobs around Atlanta and filter for .NET developer ones. I believe the first should be faster. You can also store the job locations directly in Lucene, and incorporate them in the search. A rough draft is: Indexing: 1. When you receive a new 'wanted' ad, find its geo-location using the database. 2. Store the location as a Lucene field in the ad's document. Retrieval: 1. Retrieve all jobs according to textual matches. 2. Use geometrical calculations for finding distances between the user's place and the job location. 3. Filter jobs according to distance.</p> <p><a href="http://www.manning.com/hatcher2/" rel="nofollow noreferrer">Lucene in Action</a> has an example of spatial search similar in spirit. <a href="http://www.manning.com/hatcher3/" rel="nofollow noreferrer">A second edition</a> is in the making. Also, check out <a href="http://sujitpal.blogspot.com/2008/02/spatial-search-with-lucene.html" rel="nofollow noreferrer">Sujit Pal's suggestions for spatial search with Lucene</a> and <a href="http://www.nsshutdown.com/projects/lucene/whitepaper/locallucene_v2.html" rel="nofollow noreferrer">Patrick O'Leary's framework</a>. There are also <a href="http://locallucene.wiki.sourceforge.net/" rel="nofollow noreferrer">Locallucene</a> and <a href="http://www.gissearch.com/localsolr" rel="nofollow noreferrer">LocalSolr</a>, but I do not know how mature they are.</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POImproving performance of Location based search using Lucene
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USYuval F
UserOwnerUserId
1. USYuval F
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POImproving performance of Location based search using Lucene
  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
  VTAcceptedByOriginator
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.