[SERVER-34052] Require 'startTransaction':true on first operation of a multi-statement transaction Created: 21/Mar/18  Updated: 29/Oct/23  Resolved: 04/Apr/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.7.4

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: William Schultz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-34073 Allow creating transactions with read... Closed
Related
related to CSHARP-2473 Multiple startTransaction: true for s... Closed
is related to SERVER-34051 Require autocommit:false on all opera... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-04-09
Participants:

 Comments   
Comment by Ivan Artemov [ 08/Jan/19 ]

Why you can't encapsulate knowledge about transactions into sessions? Why operations and mongo drivers must operate this argument? 

Comment by William Schultz (Inactive) [ 04/Apr/18 ]

Author:

{'email': 'william.schultz@mongodb.com', 'name': 'William Schultz', 'username': 'will62794'}

Message: SERVER-34051 Require autocommit=false on all transaction operations and add support
for 'startTransaction' argument

This patch requires all operations that are part of a multi-statement transaction to
specify an autocommit=false command argument. It also adds the 'startTransaction'
command argument, which when specified as 'true' indicates that a command is
the beginning of a multi-statement transaction.
Branch: master
https://github.com/mongodb/mongo/commit/66c537372c0aa54819adb7f72c9eda6cf8750f8e

Comment by William Schultz (Inactive) [ 02/Apr/18 ]

Code review url: http://mongodbcr.appspot.com/190820001

Generated at Thu Feb 08 04:35:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.