View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003287 | Composr | core_database_drivers | public | 2017-05-16 22:40 | 2022-08-15 00:33 |
| Reporter | Chris Graham | Assigned To | |||
| Severity | Feature-request | ||||
| Status | non-assigned | Resolution | open | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0003287: Database transaction support | ||||
| Description | I go back and forth on this. I don't think we have any real need for it, but it would be a nice to have. If we do implement it we'll need to go through a lot of code to decide what should be in a transaction, and make sure automatic rollback works properly. | ||||
| Tags | No tags attached. | ||||
| Time estimation (hours) | 16 | ||||
| Sponsorship open | |||||
|
|
A point of note is that you can make a transaction last a full web request, and then database replication can tag queries from a particular transaction - making resolving conflicts easier. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-05-16 22:40 | Chris Graham | New Issue | |
| 2022-08-15 00:33 | Chris Graham | Note Added: 0007442 |
