Changes between Version 5 and Version 6 of P7
- Timestamp:
- 05/12/26 01:51:03 (2 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
P7
v5 v6 15 15 16 16 The advanced database objects are implemented on top of the normalized relational schema developed in Phase P2 and validated through the prototype application in Phase P4. 17 18 Technical Environment 19 20 || Component || Technology || 21 || Database Engine || PostgreSQL 15 || 22 || SQL Language || PostgreSQL SQL / PLpgSQL || 23 || Database Management || pgAdmin 4 || 24 || Application Layer || Flask REST API || 25 || Character Encoding || UTF-8 || 26 27 Objectives 28 29 * enforce advanced business rules directly inside the database 30 * prevent resource booking conflicts 31 * improve database consistency and integrity 32 * support analytical reporting through SQL views 33 * centralize validation logic in PostgreSQL 17 34 18 35 == Development History == … … 34 51 || Additional Constraints || Multiple || 35 52 36 == SQL Scripts == 53 SQL Scripts 37 54 38 * advanced_triggers.sql 39 * advanced_functions.sql 40 * advanced_views.sql 41 * advanced_constraints.sql 42 * advanced_testing.sql 55 || Script Name || Description || 56 || advanced_triggers.sql || Contains trigger functions and trigger definitions for booking validation and attendance consistency || 57 || advanced_functions.sql || Contains reusable SQL functions and stored procedures for calculations and reporting || 58 || advanced_views.sql || Contains analytical SQL views used for financial and operational summaries || 59 || advanced_constraints.sql || Contains additional CHECK and UNIQUE constraints || 60 || advanced_testing.sql || Contains SQL testing scenarios for validating triggers and constraints || 43 61 44 62 == Contents == … … 58 76 === [[Testing and Validation]] === 59 77 This section contains example SQL testing scenarios used to validate the advanced database functionality. 78 79 Summary 80 81 This phase successfully introduced advanced PostgreSQL database functionality into the Wedding Planner Management System. 82 83 The implementation includes trigger-based validation, reusable SQL functions, analytical views, and additional integrity constraints used to enforce business rules directly inside the database layer. 84 85 The advanced SQL functionality improves data consistency, reduces application-level complexity, and supports analytical reporting for wedding management operations. 86 87 Additional Notes 88 89 * All trigger functions are implemented using PL/pgSQL. 90 * Validation logic is executed automatically during INSERT and UPDATE operations. 91 * SQL views are used to simplify analytical reporting. 92 * Constraints are implemented directly at database level for stronger integrity enforcement.
