party-tph-catalog

TPH inheritance allows you to manage polymorphic catalog dimensions using a single database table with a discriminator string. This centralizes shared fields like audit trails and soft deletes, eliminating the need for full entity scaffolding for each small catalog.

TPH (Table Per Hierarchy) is an Entity Framework Core mapping strategy that uses a discriminator column to differentiate entity types in a single table. Use it for small catalog dimensions to share audit fields, state, and CRUD logic without requiring extra join tables.

Yes, this TPH catalog management approach implements CRUD operations and permissions directly without requiring additional join tables. By inheriting DTOs and services from base classes, it handles shared state and access rules within the single-table structure.

The best way to create a new polymorphic catalog entity is to inherit from the base TPH classes for entities, DTOs, and services. You then register the new entity with a specific discriminator string in Entity Framework Core to activate its CRUD operations and shared state management.

Yes, Entity Framework Core is required because it handles the table operations and discriminator registration essential for TPH inheritance. The framework manages the single-table mapping and shared state logic that streamline polymorphic catalog dimensions.