Details
-
Improvement
-
Resolution: Won't Fix
-
Major
-
sdk-3.2
-
DOC-2021-Aug01-S15, DOC-2021-Aug15-S16, DOC-2021-Aug29-S17, DOC-2021-Sep12-S18, DOC-2021-Sep26-S19, DOC-2021-Oct10-S20, DOC-2021-Oct24-S21, DOC-2021-Nov07-S22, DOC-2021-Nov21-S23, DOC-2021-Dec05-S24, DOC-2021-Dec19-S25, DOC-2021-Dec31-S26, DOC-2022-S1, DOC-2022-S2, DOC-2022-S3, DOC-2022-S4, DOC-2022-S5, DOC-2022-S6, DOC-2022-S7, DOC-2022-S8, DOC-2022-S9, DOC-2022-S10, DOC-2022-S11, DOC-2022-S12, DOC-2022-S13, DOC-2022-S14, DOC-2022-S15, DOC-2022-S16, DOC-2022-S17, DOC-2022-S18, DOC-2022-S19
-
3
Description
To cover:
- What transactions implementations support what features. The transactions 2.0/2.1 labelling was created for exactly this, so we can bundle together internal Extension labels into a user-facing overall product.
- How transaction implementations interop. Essentially - perfectly. But let's spell it out, and users may be curious about how an implementation with ExtQuery could interop with an implementation without it, in terms of MAV reads etc. (Spoiler - also perfectly)
Attachments
Issue Links
- relates to
-
DOC-9296 Transactions in Durability docs
- Closed