StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1999055
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-01-04T11:48:57.323
FavoriteCount
0
LastActivityDate
2010-01-04T11:48:57.323
LastEditDate
LastEditorUserId
0
OwnerUserId
243134
ParentId
1657805
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
You've asked a number of questions at once, but I'll do the best I can to answer them. <ul> <li>Marking a service as @Transactional associates it with the current JTA (Java Transaction API) transaction (or creates one if required)</li> <li>Depending on how your datasources are configured, JDBC connections will typically also be associated (enlisted) into the transaction</li> <li>If a connection is associated with a JTA transaction then anything that is executed on it will take place within a database transaction.</li> <li>In Sybase ASE, you cannot create (or drop) a table inside a transaction.</li> </ul> So, marking your service as @Transactional will prevent you from executing a proc that contains create table statements. However, that won't solve the problem you're facing anyway. Marking something @Transactional, simply means that it executes inside a JTA transaction. And that means that it either commits, or rolls-back, but it doesn't guard against concurrent access. You have a few options <ul> <li>If you know that your application will only ever run on a single VM, then you can mark the code as <code>serialized</code>. This will make sure the VM only ever has 1 thread inside that code at a time.</li> <li>You can implement concurrency controls inside the proc, (e.g. use <code>lock table</code>), but that will require a transaction, which will prevent you from creating a table inside the procedure.</li> <li>Or you can redesign your application to not have to jump through all these hoops.</li> </ul> There are probably easier ways of achieving the outcome you're looking for - creating and dropping tables inside a proc, and then trying to prevent concurrent access to that proc is not a typical way of solving a problem.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSpring Transaction with Sybase
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USTim
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. 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.