Files
worklenz/worklenz-backend/database
chamikaJ b320a7b260 feat(project-finance): enhance project finance view and calculations
- Added a new SQL view `project_finance_view` to aggregate project financial data.
- Updated `project-finance-controller.ts` to fetch and group tasks by status, priority, or phases, including financial calculations for estimated costs, actual costs, and variances.
- Enhanced frontend components to display total time logged, estimated costs, and fixed costs in the finance table.
- Introduced new utility functions for formatting hours and calculating totals.
- Updated localization files to include new financial columns in English, Spanish, and Portuguese.
- Implemented Redux slice for managing project finance state and actions for updating task costs.
2025-05-23 08:32:48 +05:30
..
2025-04-17 18:28:54 +05:30
2025-04-17 18:28:54 +05:30

All database DDLs, DMLs and migrations relates to the application should be stored here as well.

Worklenz Database

Directory Structure

  • sql/ - Contains all SQL files needed for database initialization
  • migrations/ - Contains database migration scripts
  • 00-init-db.sh - Initialization script that executes SQL files in the correct order

SQL File Execution Order

The database initialization files should be executed in the following order:

  1. sql/0_extensions.sql - PostgreSQL extensions
  2. sql/1_tables.sql - Table definitions and constraints
  3. sql/indexes.sql - All database indexes
  4. sql/4_functions.sql - Database functions
  5. sql/triggers.sql - Database triggers
  6. sql/3_views.sql - Database views
  7. sql/2_dml.sql - Data Manipulation Language statements (inserts, updates)
  8. sql/5_database_user.sql - Database user setup

Docker-based Setup

In the Docker environment, we use a shell script called 00-init-db.sh to control the SQL file execution order:

  1. The shell script creates a sql/ subdirectory if it doesn't exist
  2. It copies all .sql files into this subdirectory
  3. It executes the SQL files from the subdirectory in the correct order

This approach prevents the SQL files from being executed twice by Docker's automatic initialization mechanism, which would cause errors for objects that already exist.

Manual Setup

If you're setting up the database manually, please follow the execution order listed above. Ensure your SQL files are in the sql/ subdirectory before executing the script.