StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14301438
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-13T07:10:30.323
FavoriteCount
0
LastActivityDate
2013-01-13T07:10:30.323
LastEditDate
LastEditorUserId
0
OwnerUserId
1679310
ParentId
14299456
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
The behaviour you've described is correct (<a href="http://nhibernate.hibernatingrhinos.com/28/first-and-second-level-caching-in-nhibernate">more here</a>). <blockquote> The update timestamp cache is not updated until you commit the transaction! This is to ensure that you will not read "uncommitted values" from the cache. </blockquote> Whenever there is a change on a <code>type</code> which we've got in Cache - cached data are stale... until the complete transaction is commited. Imagine that you've cached results of this filter: <pre><code> var query = (from w in session.Query<Widget>().Cacheable() where w.Name == "B*" // all names starting with B select w); </code></pre> And later will add new Widget: <pre><code>var widget = new Widget {Name = "Brigitte"}; session.Save(widget); // explicit Flush is not needed, // but then, until Commit(), query will never return Brigitte session.Flush(); // to immediately execute INSERT </code></pre> If the query would be still cached, Brigitte will never appear... And while in Transaction, queries with FirstOrDefault() are executed immediately - the write operations could wait for a Flush on Commit. Because of the Transaction, all contained operations (insert, udpate, select) cannot profit from caching, because only Transaction as a batch makes sense. So until commit is called, no cache could be used. Many detailed and very helpful information could be found here: <a href="http://nhibernate.hibernatingrhinos.com/28/first-and-second-level-caching-in-nhibernate">First and Second Level caching in NHibernate</a> <blockquote> The timestamp cache is updated whenever a table is written to, but in a tricky sort of way: <ul> <li>When we perform the actual writing, we write a value that is somewhere in the future to the cache. So all queries that hit the cache now will not find it, and then hit the DB to get the new data. Since we are in the middle of transaction, they would wait until we finish the transaction. If we are using low isolation level, and another thread / machine attempts to put the old results back in the cache, it wouldn't hold, because the update timestamp is into the future.</li> <li>When we perform the commit on the transaction, we update the timestamp cache with the current value.</li> </ul> </blockquote>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONHibernate - Query misses the query cache after saving a new entity
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRadim Köhler
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PONHibernate - Query misses the query cache after saving a new entity
 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.