Steven Masley 854044e811 chore: fix concurrent CommitQuota transactions for unrelated users/orgs (#15261) ...

The failure condition being fixed is `w1` and `w2` could belong
to different users, organizations, and templates and still cause a
serializable failure if run concurrently. This is because the old query 
did a `seq scan` on the `workspace_builds` table. Since that is the 
table being updated, we really want to prevent that.

So before this would fail for any 2 workspaces. Now it only fails if
`w1` and `w2` are owned by the same user and organization.

2024-11-01 11:05:49 -04:00

..

dbmock.go

chore: fix concurrent CommitQuota transactions for unrelated users/orgs (#15261)

2024-11-01 11:05:49 -04:00

doc.go

chore: add /v2 to import module path (#9072)

2023-08-18 18:55:43 +00:00