worker-role-database

Database migrations across ArangoDB and PostgreSQL are coordinated by using arangojs for ArangoDB and Prisma for PostgreSQL. This approach enforces strict safety rules, requiring backups before destructive operations and verifying changes after execution to ensure data integrity.

Safe schema changes in mixed database environments require automated validation, backup creation, and rollback planning. The process orchestrates migrations via Prisma, logs all actions for traceability, and conducts post-change checks to guarantee data correctness across different environments.

Yes, seed data management and verification are fully supported. The workflow applies seed data operations and executes post-change checks to ensure data correctness and consistency across all targeted database environments after migrations are completed.

No, running raw queries is strictly prohibited unless explicitly instructed. The workflow mandates using arangojs for ArangoDB and Prisma for PostgreSQL to execute schema changes, ensuring all operations remain safe, traceable, and validated.

Backups are automatically required before any destructive database operations are executed. The system enforces this safety rule by initiating backups prior to schema changes and validating the results after every modification to prevent data loss.

Prisma and arangojs are required to enforce safe, automated schema changes for PostgreSQL and ArangoDB respectively. Using these dedicated clients prevents unsafe raw queries, ensures strict validation, and maintains traceability during data operations.