StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5223807
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-03-07T18:51:47.823
FavoriteCount
0
LastActivityDate
2011-03-07T18:51:47.823
LastEditDate
LastEditorUserId
0
OwnerUserId
8655
ParentId
5222756
PostTypeId
2
Score
14
ViewCount
0
LastEditorDisplayName
text
Body
Actually there isn't two competing client-side databases being built into modern browsers, the Web SQL standard has been discontinued, in future versions of browsers there will only(*) be IndexedDB. Firefox will <a href="https://developer.mozilla.org/en/IndexedDB">have it in 4.0</a>, Chrome will have it <a href="http://src.chromium.org/viewvc/chrome?view=rev&revision=62092">sometime</a>, IE will have it <a href="http://html5labs.interoperabilitybridges.com/prototypes/available-for-download/indexeddb">some time later</a> and Opera will (so I've heard) have it in 11.50 (*)I say only, but I'm willing to bet WebKit will continue to support Web SQL for some time to come given that there's significant existing use out there, especially on iOS targeted stuff. My personal opinion is that not blessing SQLite as a web standard is a good thing, but IndexedDB is not the thing to directly replace it. It's too low level to be really comfortable for front end developers to think about in the same way as SQL (if you've ever done that 'show execution plan' thing in SQL Server Studio, IndexedDB is basically the sort of thing you see there except without the handy diagrammatic comprehension aid). Having not yet devoted a serious chunk of time to understanding it, I haven't yet been able to figure out how to write a useful application with IndexedDB. My feeling is that it won't really take off until we see something like jQueryDB or possibly jsHibernate. In the meantime, if a significant chunk of your users will be WebKit based, stick with Web SQL.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWeb SQL Database or Indexed Database API ... or both?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USrobertc
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWeb SQL Database or Indexed Database API ... or both?
 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
 VTAcceptedByOriginator
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.