further rename

Author: 3nids

BACKWARD_COMPATIBILITY.md

@@ -8,7 +8,7 @@ PUM now supports reading legacy `.pum.yaml` files that use the old field names `
 
 The refactoring renamed hook-related fields for better clarity:
 - **Old**: `migration_hooks` with `pre`/`post` hooks
-- **New**: `application_hooks` with `drop`/`create` hooks
+- **New**: `application` with `drop`/`create` hooks
 
 ## Future Considerations
 

README.md

@@ -16,7 +16,7 @@ PUM (PostgreSQL Upgrades Manager) is a robust database migration management tool
 - **Command-line and Python Integration**: Use PUM as a standalone CLI tool or integrate it into your Python project.
 - **Database Versioning**: Automatically manage database versioning with a metadata table.
 - **Changelog Management**: Apply and track SQL delta files for database upgrades.
-- **Migration Hooks**: Define custom hooks to execute additional SQL or Python code to drop or create the application schema during migrations. This feature allows you to isolate data (table) code from application code (such as views and triggers), ensuring a clear separation of concerns and more maintainable database structures.
+- **Migration Hooks**: Define custom hooks to execute additional SQL or Python code to drop or create the application during migrations. This feature allows you to isolate data (table) code from application code (such as views and triggers), ensuring a clear separation of concerns and more maintainable database structures.
 
 ## Why PUM?
 

docs/docs/hooks.md docs/docs/application.mddocs/docs/hooks.md renamed to docs/docs/application.md

@@ -1,18 +1,26 @@
-# Migration hooks
+# Application
 
-Migration hooks allow you to define actions to be executed during the migration process. These hooks are defined in the `.pum.yaml` configuration file under the `application_hooks` section.
+## Application/data isolation
+
+Separating application logic from object (business) data is recommended. Place application-owned objects—such as views, functions, procedures, and triggers—into dedicated, application-specific schemas, while keeping persistent business tables in one or several separate data schemas.
+
+This isolation makes application artifacts clearly distinct from long-lived data, so application schemas can be dropped and recreated on demand (for rebuilds, upgrades, or environment resets) without impacting the underlying object data.
+
+Application hooks allow you to define actions to be executed during the migration process.
+They allow the creation and removal of the application part of the data model.
+These hooks are defined in the `.pum.yaml` configuration file under the `application` section.
 
 There are two types of migration hooks:
 
-- `drop`: Hooks to drop the application schema before applying migrations.
-- `create`: Hooks to create the application schema after applying migrations.
+- `drop`: Hooks to drop the application before applying migrations.
+- `create`: Hooks to create the application after applying migrations.
 
 ## SQL hooks
 
 Hooks are defined as a list of files or plain SQL code to be executed. For example:
 
 ```yaml
-application_hooks:
+application:
   drop:
     - code: DROP VIEW IF EXISTS pum_test_app.some_view;
 
@@ -32,7 +40,7 @@ You can use `pum.utils.execute_sql` to execute the SQL code without committing.
 The configuration is then:
 
 ```yaml
-application_hooks:
+application:
   drop:
     - file: drop_app/drop_view.sql
 

docs/docs/configuration/application_hooks_model.md

@@ -0,0 +1,3 @@
+# ApplicationModel
+
+::: pum.config_model.ApplicationModel

docs/docs/configuration/application_model.md

@@ -6,7 +6,7 @@ In the config file `.pum.yaml`, you can define, with the YAML syntax:
 
 * `changelogs_directory`: the directory with the changelogs files.
 * `parameters`: the definition of parameters for the migration.
-* `application_hooks`: the `drop` and `create` application schema hooks.
+* `application`: the `drop` and `create` application hooks.
 
 For example:  
 ```yaml

docs/docs/configuration/configuration.md

@@ -72,13 +72,13 @@ nav:
       - ConfigModel: configuration/config_model.md
       - DependencyModel: configuration/dependency_model.md
       - HookModel: configuration/hook_model.md
-      - ApplicationHookModel: configuration/application_hooks_model.md
+      - ApplicationModel: configuration/application_model.md
       - ParameterDefinitionModel: configuration/parameter_definition_model.md
       - PermissionModel: configuration/permission_model.md
       - PumModel: configuration/pum_model.md
       - RoleModel: configuration/role_model.md
 
-  - Hooks: hooks.md
+  - Application: application.md
   - Roles: roles.md
   - CLI:
       - Overview: cli.md

docs/mkdocs.yml

@@ -54,13 +54,13 @@ def validate_args(self):
         return self
 
 
-class ApplicationHookModel(PumCustomBaseModel):
+class ApplicationModel(PumCustomBaseModel):
     """
-    ApplicationHookModel holds the configuration for application schema hooks.
+    ApplicationModel holds the configuration for application hooks.
 
     Attributes:
-        drop: Hooks to drop the application schema before applying migrations.
-        create: Hooks to create the application schema after applying migrations.
+        drop: Hooks to drop the application before applying migrations.
+        create: Hooks to create the application after applying migrations.
     """
 
     drop: Optional[List[HookModel]] = Field(default=[], alias="pre")
@@ -197,15 +197,15 @@ class ConfigModel(PumCustomBaseModel):
     Attributes:
         pum: The PUM (Project Update Manager) configuration. Defaults to a new PumModel instance.
         parameters: List of parameter definitions. Defaults to an empty list.
-        application_hooks: Configuration for application schema hooks. Defaults to a new ApplicationHookModel instance.
+        application: Configuration for application hooks. Defaults to a new ApplicationModel instance.
         changelogs_directory: Directory path for changelogs. Defaults to "changelogs".
         roles: List of role definitions. Defaults to None.
     """
 
     pum: Optional[PumModel] = Field(default_factory=PumModel)
     parameters: Optional[List[ParameterDefinitionModel]] = []
-    application_hooks: Optional[ApplicationHookModel] = Field(
-        default_factory=ApplicationHookModel, alias="migration_hooks"
+    application: Optional[ApplicationModel] = Field(
+        default_factory=ApplicationModel, alias="migration_hooks"
     )
     changelogs_directory: Optional[str] = "changelogs"
     roles: Optional[List[RoleModel]] = []
@@ -216,6 +216,6 @@ class ConfigModel(PumCustomBaseModel):
     def handle_legacy_field_names(cls, values):
         """Support legacy field names for backward compatibility."""
         # If new name doesn't exist but old name does, use old name
-        if "application_hooks" not in values and "migration_hooks" in values:
-            values["application_hooks"] = values.pop("migration_hooks")
+        if "application" not in values and "migration_hooks" in values:
+            values["application"] = values.pop("migration_hooks")
         return values

pum/config_model.py

@@ -250,9 +250,9 @@ def drop_app_handlers(self) -> list[HookHandler]:
         return (
             [
                 HookHandler(base_path=self._base_path, **hook.model_dump())
-                for hook in self.config.application_hooks.drop
+                for hook in self.config.application.drop
             ]
-            if self.config.application_hooks.drop
+            if self.config.application.drop
             else []
         )
 
@@ -261,9 +261,9 @@ def create_app_handlers(self) -> list[HookHandler]:
         return (
             [
                 HookHandler(base_path=self._base_path, **hook.model_dump())
-                for hook in self.config.application_hooks.create
+                for hook in self.config.application.create
             ]
-            if self.config.application_hooks.create
+            if self.config.application.create
             else []
         )
 
@@ -311,9 +311,9 @@ def validate(self, install_dependencies: bool = False) -> None:
                 raise PumInvalidChangelog(f"Changelog `{changelog}` is invalid.") from e
 
         hook_handlers = []
-        if self.config.application_hooks.drop:
+        if self.config.application.drop:
             hook_handlers.extend(self.drop_app_handlers())
-        if self.config.application_hooks.create:
+        if self.config.application.create:
             hook_handlers.extend(self.create_app_handlers())
         for hook_handler in hook_handlers:
             try: