StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8453824
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-12-10T01:59:33.093
FavoriteCount
0
LastActivityDate
2011-12-10T01:59:33.093
LastEditDate
LastEditorUserId
0
OwnerUserId
586748
ParentId
8453612
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You're right, I think this would be an interesting project. There are loads of approaches you could take to this. One would be to create a <code>Query</code> object that you build up by calling the methods in turn. So something like this: <pre><code>public class Query { public static Query select(String...fields){ //code omitted return query; } public Query from(Collection<Object> collection){ //code omitted return this; } public Query where(String field, Object value){ //code omitted return this; } } </code></pre> So you could then do: <pre><code>Query.select("field1", "field2").from(myList).... </code></pre> You'd need to keep track of which values had been selected at each point and whether they next condition should add to them (as in the case of an <code>or</code>) or remove from them (as in the case of an <code>and</code>). There will be lots of edge cases. My advice would be to start off with something very simple like the <code>ints</code> example and work from there. When you get on to doing the object version you'll need to use <a href="http://en.wikipedia.org/wiki/Reflection_%28computer_programming%29" rel="nofollow">reflection</a> to access the fields of the object. Once you've done that you might want to consider improving the type safety of your code by using <a href="http://en.wikipedia.org/wiki/Generics_in_Java" rel="nofollow">generics</a>. All in all, lots of scope for an interesting project. However, it feels like the sort of thing where there will be lots of edge cases, so worth thinking through the design a fair bit and would also not be a bad idea to do a fair bit of <a href="http://en.wikipedia.org/wiki/Unit_testing" rel="nofollow">unit testing.</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POJava SQL-style Array Manipulation
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRussell
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POJava SQL-style Array Manipulation
 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
CommentsPostId
1. COGreat explanation! I was thinking of using reflection, and I like the idea of using a class like `Query` instead of just making a set of functions.
 singulars
 PostPostId
 PO
 UserUserId
 USJon

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.