StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12096376
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-08-23T16:39:14.083
FavoriteCount
0
LastActivityDate
2018-06-13T22:52:49.497
LastEditDate
2018-06-13T22:52:49.497
LastEditorUserId
41010
OwnerUserId
41010
ParentId
2212230
PostTypeId
2
Score
12
ViewCount
0
LastEditorDisplayName
text
Body
<a href="http://en.wikipedia.org/wiki/NoSQL" rel="nofollow noreferrer">NoSQL</a> covers a diverse set of tools and services, including key-value-, document, graph and wide-column stores. They usually try improving scalability of the data store, usually by distributing data processing. Transactions require <a href="http://en.wikipedia.org/wiki/ACID" rel="nofollow noreferrer">ACID</a> properties of how DBs perform user operations. ACID restricts how scalability can be improved: most of the NoSQL tools relax consistency criteria of the operatioins to get fault-tolerance and availability for scaling, which makes implementing ACID transactions very hard. A commonly cited theoretical reasoning of distributed data stores is the <a href="http://en.wikipedia.org/wiki/CAP_theorem" rel="nofollow noreferrer">CAP theorem</a>: consistency, availability and partition tolerance cannot be achieved at the same time. SQL, NoSQL and NewSQL tools can be classified according to what they give up; a good figure might be found <a href="http://blog.nahurst.com/visual-guide-to-nosql-systems" rel="nofollow noreferrer">here</a>. A new, weaker set of requirements replacing ACID is <a href="http://en.wikipedia.org/wiki/Eventual_consistency" rel="nofollow noreferrer">BASE</a> ("basically avalilable, soft state, eventual consistency"). However, eventually consistent tools ("eventually all accesses to an item will return the last updated value") are hardly acceptable in transactional applications like banking. Here a good idea would be to use in-memory, column-oriented and distributed SQL/ACID databases, for example <a href="http://voltdb.com/" rel="nofollow noreferrer">VoltDB</a>; I suggest looking at these "NewSQL" solutions.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POTransactions in NoSQL?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. UScsaba
UserOwnerUserId
1. UScsaba
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
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.