db: test suite for routines, triggers and rollbacks #6

Open
opened 2026-11-15 22:24:07 -05:00 by forgejo_admin · 2 comments
Owner

Prove the transactional behaviour the rubric grades.

  • db/tests/*.sql: one file per routine group; each case asserts with SIGNAL on failure
  • Admin and termination: reason checks, grace bounds, appeal pauses execution, execution deletes only sole-owned projects (co-owned and shared survive), notice required before execution
  • Every guard: last owner, job state machine, folder root/cycle, share-link role cap, invitation email binding, quota
  • Rollback: a failing call leaves no partial rows (blobs, folders, files)
  • SKIP LOCKED: two sessions claiming concurrently never get the same job
  • Runs on MariaDB 11.4 and MySQL 8.4 (CI wires it, #2)

Conventions — CLAUDE.md and PLAN.md at the repo root.

Prove the transactional behaviour the rubric grades. - [ ] `db/tests/*.sql`: one file per routine group; each case asserts with `SIGNAL` on failure - [ ] Admin and termination: reason checks, grace bounds, appeal pauses execution, execution deletes only sole-owned projects (co-owned and shared survive), notice required before execution - [ ] Every guard: last owner, job state machine, folder root/cycle, share-link role cap, invitation email binding, quota - [ ] Rollback: a failing call leaves no partial rows (blobs, folders, files) - [ ] `SKIP LOCKED`: two sessions claiming concurrently never get the same job - [ ] Runs on MariaDB 11.4 and MySQL 8.4 (CI wires it, #2) **Conventions** — CLAUDE.md and PLAN.md at the repo root.
Collaborator

@liam this issue blocks #50, #31, #19 and has not been started (16 h).

— automation (scripts/watch.py)

@liam this issue blocks #50, #31, #19 and has not been started (16 h). — automation (scripts/watch.py) <!-- watch:ready:2026-11-17T00:00:00+00:00:1 -->
Collaborator

@liam this issue blocks #50, #31, #19 and has not been started (32 h). Escalated to #40.

— automation (scripts/watch.py)

@liam this issue blocks #50, #31, #19 and has not been started (32 h). Escalated to #40. — automation (scripts/watch.py) <!-- watch:ready:2026-11-17T00:00:00+00:00:2 -->
Sign in to join this conversation.
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.

Reference
k8s-services/dongba#6
No description provided.