StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14880096
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-02-14T17:00:06.047
FavoriteCount
0
LastActivityDate
2013-02-14T18:05:32.013
LastEditDate
2013-02-14T18:05:32.013
LastEditorUserId
551467
OwnerUserId
551467
ParentId
14879878
PostTypeId
2
Score
14
ViewCount
0
LastEditorDisplayName
text
Body
I would suggest accepting the date as a <code>String</code> and parsing it yourself. Like so: <pre><code>@GET @Path("/generateInfo") @Produces(MediaType.APPLICATION_JSON) public String generateInfo( @QueryParam("a") String a, @QueryParam("b") String b, @QueryParam("date") String date) { SimpleDateFormat sdf = new SimpleDateFormat("yyyy-MM-dd"); Date dateObj = sdf.parse(date); return "hello world"; }</code></pre> The way to make this request via a browser is: <pre><code>http://localhost/your_service/generateInfo?date=2013-02-14</code></pre> Things to consider when parsing dates: <ul> <li><code>SimpleDateFormat</code> is very flexible with parsing different date formats. The <a href="http://en.wikipedia.org/wiki/ISO_8601">ISO standard for date</a> strings is: <code>yyyy-MM-dd</code></li> <li>The <a href="http://joda-time.sourceforge.net/">Joda Java date API</a> is accepted as a more complete implementation of date/time, and <a href="http://mike-java.blogspot.co.uk/2008/02/java-date-time-api-vs-joda.html">some believe that it is more optimised than Java's native date API</a> particularly for parsing dates.</li> <li>it is often better to provide dates as epoch timestamps, especially if your application operates over different timezones. However, you must be aware of HTTP caching issues when accepting epoch timestamps (e.g. if your clients are not truncating epoch timestamps then you will get lots of cache misses). I would refer back to <a href="http://en.wikipedia.org/wiki/ISO_8601">ISO-8601</a> as formatted dates are easier to HTTP cache.</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POConsume Restful method from URL with Date Param Java
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USpestrella
UserOwnerUserId
1. USpestrella
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POConsume Restful method from URL with Date Param Java
 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. COThis is the preferred way IMHO. Your JSON marshaller most likely will break down the `Date` class into it's fields, so you'd end up with an object `Date` in your JSON, rather then a neat `String`.
 singulars
 PostPostId
 PO
 UserUserId
 USNicholas

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.