Skip to content

fix: Schema drift reconciliation#365

Merged
greatest0fallt1me merged 1 commit into
CalloraOrg:mainfrom
Onyedika3d:task/schema-drift-reconciliation
May 28, 2026
Merged

fix: Schema drift reconciliation#365
greatest0fallt1me merged 1 commit into
CalloraOrg:mainfrom
Onyedika3d:task/schema-drift-reconciliation

Conversation

@Onyedika3d
Copy link
Copy Markdown

PR Summary — Schema Drift Reconciliation (#304)

Summary

Defined and enforced a clear ownership boundary between Prisma (Postgres) and Drizzle + SQLite (dashboard entities) to eliminate silent schema drift and make schema ownership explicit.

The schema drift test suite has been strengthened to detect:

  • ORM table ownership overlap
  • Unexpected tables in either schema
  • SQLite migration/schema inconsistencies
  • UUID compatibility issues between cross-database references

Documentation has also been updated to reflect the final architectural decision and ongoing drift-prevention strategy.

Ownership Boundary (Single Source of Truth)

Prisma + Postgres

Owns:

users

Drizzle + SQLite

Owns:

developers
apis
api_endpoints

Closes: #304

@drips-wave
Copy link
Copy Markdown

drips-wave Bot commented May 28, 2026

@Onyedika3d Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@greatest0fallt1me greatest0fallt1me merged commit 7348588 into CalloraOrg:main May 28, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Reconcile Prisma users schema with the Drizzle developers/apis/api_endpoints tables to remove schema drift

2 participants