How myanex/gestioninnorov works
Project type and purpose
• This is a database‐centric project (“GestionInnoRov”) whose sole deliverable is a managed set of SQL artifacts (baseline schemas, incremental migrations, preflight smoke tests, seed data and views).
• There is no application code; the project’s objective is to version, validate and deploy database changes safely across environments.
File structure
• Top‐level “db/” folder contains all artifacts:
• Scripts/ – catch‐all SQL files
• baselines/ – initial schema snapshots
• migrations/ – ordered DDL/DML changesets
• preflight/ – scripts to validate migrations (smoke tests)
• seeds/ – demo/test data loaders
• logs/ – migration run history
• maintenance/ – housekeeping or archive scripts
• views/ – presentation layer SQL objects
• Project root has only editor/config files and README.
README for additional insights
• Implicit stack: relational database (e.g. PostgreSQL, SQL Server) managed via DBeaver and source control.