Improve All Business Logics That Make More Than One DB Calls To Avoid Partial Data Insertions, Using DB Transactions.

[elraphty]

Context

Currently, we catch individual DB call errors, when we work on a business logic that requires more than one insert or update call, which may lead to partial database data.

e.g

p, err := oh.db.CreateOrEditWorkspaceRepository(workspaceRepo)
if err != nil {
    w.WriteHeader(HTTP.StatusBadRequest)
    return
}

we return out of process if any error is found.

Design

We want to use database transactions to perform such chain database calls, to avoid any partial data in the database.

These are the important business logic to look at:

• MakeBountyPayment
• WithdrawBudget
• GenerateBudgetInvoice
• GenerateInvoice
• DeleteWorkspace
• PollBudgetInvoices
• PollUserWorkspacesBudge

Acceptance Criteria

• I've tested on Chrome
• I've created a test that...
• I have rebased and tested locally before submitting my PR
• I can submit a PR within 2 days of taking the bounty

Here is an example backend test