StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POUnable to Isolate Transactions Across Tiers in Postgres / JDBC
primarykey
Id
10404262
data
AcceptedAnswerId
10404603
AnswerCount
2
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2012-05-01T20:58:31.087
FavoriteCount
0
LastActivityDate
2012-05-02T01:35:39.833
LastEditDate
LastEditorUserId
0
OwnerUserId
212950
ParentId
0
PostTypeId
1
Score
1
ViewCount
467
LastEditorDisplayName
text
Body
I'm working on a Java project that incorporates a PostgresSQL 9.0 database tier, using JDBC. SQL is wrapped in functions, executed in Java like stored procedures using JDBC. The database requires a header-detail scheme, with detail records requiring the foreign-key ID to the header. Thus, the header row is written first, then a couple thousand detail records. I need to prevent the user from accessing the header until the details have completed writing. You may suggest wrapping the entire transaction so that the header record cannot be committed until the detail records have completed writing. However, you can see below that I've isolated the transactions to calls in Java: write header, then loop thru details (while writing detail rows). Due the the sheer size of the data, it is not feasible to pass the detailed data to the function to perform one transaction. My question is: how do I wrap the transaction at the JDBC level, so that the header is not committed until the detail records have finished writing? The best solution metaphor would be SQL Server's named transaction's, where the transaction could be started in the data-access layer code (outside other transactions), and completed in a later DB call. The following (simplified) code executes without error, but doesn't resolve the isolation problem: <pre><code>DatabaseManager mgr = DatabaseManager.getInstance(); Connection conn = mgr.getConnection(); CallableStatement proc = null; conn.setAutoCommit(false); proc = conn.prepareCall("BEGIN TRANSACTION"); proc.execute(); //Write header details writeHeader(....); for(Fault fault : faultList) { writeFault(fault, buno, rsmTime, dnld, faultType, verbose); } proc = conn.prepareCall("COMMIT TRANSACTION"); proc.execute(); </code></pre> Your brilliant answer will be much appreciated!
Tags
<java><sql><postgresql><jdbc>
Title
Unable to Isolate Transactions Across Tiers in Postgres / JDBC
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMAbraham1
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POUnable to Isolate Transactions Across Tiers in Postgres / JDBC
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.