StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8088462
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-11-11T00:57:51.673
FavoriteCount
0
LastActivityDate
2011-11-15T13:03:05.413
LastEditDate
2011-11-15T13:03:05.413
LastEditorUserId
68119
OwnerUserId
68119
ParentId
5178708
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
I added comment to Spring <a href="https://jira.springsource.org/browse/SPR-6908" rel="nofollow">improvement ticket</a> on this. I'll copy it here too: I worked around this problem by converting all service methods that were declaratively setup like this <pre><code>@Transactional(propagation = REQUIRES_NEW) public Object doSmth() { // doSmthThatRequiresNewTx } </code></pre> to use <code>TransactionTemplate</code> instead: <pre><code>private TransactionTemplate transactionTemplate; public Object doSmth() { return transactionTemplate.execute(new TransactionCallback<Object>() { @Override public Object doInTransaction(TransactionStatus status) { // doSmthThatRequiresNewTx } }); } </code></pre> Under tests I configure <code>transactionTemplate</code>'s propagation behavior to be <code>PROPAGATION_REQUIRED</code>, under real app I configure <code>transactionTemplate</code>'s propagation behaviour to be <code>PROPAGATION_REQUIRES_NEW</code>. It works as expected. The limitation of this workaround is that under tests it is not possible to assert the fact that inner transaction is not rolledback in an exceptional scenario. The other solution would be to explicitly delete everything <code>doSmth()</code> does in the database in the <code>@AfterTransaction</code> method in test. That 'delete' SQL will be run in the new transaction, as its results would be otherwise rolled back routinely by Spring's <code>TransactionConfiguration</code> default behaviour.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to rollback nested transactions with Propagation.REQUIRES_NEW in integration tests
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USparxier
UserOwnerUserId
1. USparxier
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
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.