StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14024362
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-12-24T17:59:22.483
FavoriteCount
0
LastActivityDate
2012-12-24T17:59:22.483
LastEditDate
LastEditorUserId
0
OwnerUserId
908390
ParentId
14018496
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
With MarkLogic an entire XQuery update normally acts like a single transaction. When <code>mut:release</code> adds an update to the transaction's stack, the rest of the query will not see that update until after it commits. From the point of view of the query, this normally happens after the entire query finishes, and is not visible to the query. The docs have something useful to add about what <a href="http://docs.marklogic.com/xdmp:rollback" rel="nofollow">http://docs.marklogic.com/xdmp:rollback</a> does: <blockquote> When a transaction is rolled back, the current statement immediately terminates, updates made by any statement in the transaction are discarded, and the transaction terminates. </blockquote> So it isn't that the variables are demolished: it's that your program is over. I think <a href="http://docs.marklogic.com/guide/app-dev/transactions#id_15746" rel="nofollow">http://docs.marklogic.com/guide/app-dev/transactions#id_15746</a> has an example that is fairly close to your use-case: "Example: Multi-statement Transactions and Same-statement Isolation". It demonstrates how to <code>xdmp:eval</code> or <code>xdmp:invoke</code> to update a document and see the results within the same query. Test it to see that it works, then replace the <code>xdmp:commit</code> with an <code>xdmp:rollback</code>. For me the example still works. Start replacing the rest of the logic with your unit test logic, and you should be on your way.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POTesting XQuery and Marklogic transactions
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USmblakele
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POTesting XQuery and Marklogic transactions
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.