Run deletions in transactions #467

New issue

Open

opened 2019-03-12 14:07:35 +00:00 by elegaanz · 1 comment

elegaanz commented

2019-03-12 14:07:35 +00:00

(Migrated from github.com)

So that if something fails, all the previous deletions are also cancelled. I'm thinking of blog/user deletion here, for which deletion cascade have been "manually" implemented.

Plume version (and/or commit): 0.2.0

So that if something fails, all the previous deletions are also cancelled. I'm thinking of blog/user deletion here, for which deletion cascade have been "manually" implemented. Plume version (and/or commit): 0.2.0

🚀 1

trinity-1686a commented

2019-04-07 22:05:01 +00:00

Owner

It's not the only thing that we should run in transactions, for instance creating a new user is a two step process, filling some fields, then updating others. It should be done in a transaction to avoid both race conditions (create A success, create B fail, update A success), and prevent a user from having certain fields ever empty

👍 1 ❤️ 2

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Plume/Plume#467

No description provided.

Rows
Columns