Database Schema and ERD Documentation

[nursetechie]

Issue #29 — docs: Database Schema and ERD Documentation

Description

A picture is worth a thousand words. New contributors often struggle to mentalize the relationships between relational tables. Providing an Entity Relationship Diagram (ERD) and text explanations dramatically accelerates backend onboarding.

---

Requirements & Context

Implementation Expectations: Utilize a tool (e.g., Prisma ERD generator or Mermaid.js) to visually map the relationships between User, Wallet, and EscrowIntent.

Context: Document the uniqueness constraints and cascading behaviors explicitly.

---

Acceptance Criteria

• The ERD correctly visualizes 1:1 and 1:N relationships.
• The visual diagram matches the committed schema.prisma.

---

Out of Scope

• Documenting Prisma-internal shadow tables.

---

Suggested Execution

git checkout -b docs/database-schema

---

Suggested Commit Message

docs: add database schema erd and relationships documentation

---

Testing Notes

• Ensure the generated ERD is readable and properly formatted in GitHub markdown.

---

References

Prisma ERD generator packages.

---

Definition of Done

• Ready for review.

[Victorjonah-prog]

Hi team,I want to take #69 - Database Schema and ERD Documentation.Motivation: Make the database easier for new contributors to understand.Plan: Create a clean ERD (Mermaid/Prisma) showing User, Wallet, and EscrowIntent relationships + document constraints.Will deliver fast and keep it readable in GitHub markdown.

[Vetassikc]

Hi PadiPay team — I would like to apply for #69 if it is still unassigned.

At main commit 925ae824da5c7a75aedaf503bbfbd861dd67cd20, I verified that prisma/schema.prisma, the related repository layer, tests, and public docs are available. The Vartovii Repository Evidence workflow can pin the agreed commit, build a source ledger, map the User, Wallet, and EscrowIntent relationships with direct schema references, document uniqueness and cascade behaviour, and deliver a reviewable Mermaid ERD plus docs-only PR.

I will not start before confirmation. Could a maintainer confirm whether the issue is still available, how assignment works, the exact reward terms, and who owns acceptance?