Skip to main content

Database Limitations

Audience​

Developers, database engineers, QA engineers, support engineers, security engineers, solution architects, and implementation partners.

Reference Content​

This page records source-verified Workforce Scheduling persistence behavior and boundaries.

Summary​

These limitations are verified from source. Production-state items require confirmation.

Scheduling​

  • Canonical persistence models shift-policy configuration, not rosters, rotations, availability, demand, swaps, breaks, or publication.
  • Canonical Holiday persistence is Not implemented.
  • Effective configuration changes do not create automatic historical recalculation records.
  • No schedule-period or team allocation entity exists.

Persistence​

  • Canonical assignments reference shifts and employees without database foreign keys.
  • Audit/timeline use text references rather than relational constraints.
  • Queryables cross the repository boundary.
  • Some command workflows require multiple saves.
  • No scheduling-specific reporting projection or archival store was found.

Compatibility​

  • Canonical, Leave, and legacy weekly-off representations can diverge.
  • Compatibility identity adds a second shift identity.
  • Legacy times and overtime rules use text while canonical values are typed.
  • Backfill steps and completion evidence are not one transaction.
  • Production system-of-record state requires confirmation.

Concurrency​

  • No concurrency tokens or expected-version checks exist.
  • Shift/policy name checks can race.
  • Assignment overlap checks can race.
  • Shift deactivation can race with assignment creation.
  • No database temporal exclusion constraint exists.

Tenant isolation​

  • Privileged context bypasses global filters.
  • Seeders and backfill explicitly bypass filters.
  • Trusted request-context propagation requires confirmation.
  • Scalar assignment references do not enforce same-tenant relationships.
  • Legacy tenant fields are optional.

Testing​

  • No dedicated mapping, repository, migration, or persistence integration test project was found.
  • Query-filter, cascade, constraint, concurrency, and multi-save failure tests are missing.
  • Current assurance is centered on scripts and transition validators.
  • Production performance and recovery evidence was unavailable.

Governance​

  • No retention, purge, archive, or privacy-erasure job was found.
  • Migration approval, rollback, backup, and zero-downtime policy require confirmation.
  • Seeder data governance requires confirmation.
  • Database ownership during and after compatibility cutover requires confirmation.
  • Recovery objectives and audit/timeline retention are not source-defined.

Source References​

  • microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs
  • microservices/src/attendance-service/Application/Services/ShiftPolicyCommands.cs
  • microservices/src/attendance-service/Backfill/ShiftPolicyBackfillTypes.cs
  • microservices/src/leave-service/Infrastructure/LeaveDbContext.cs
  • Data/AppDbContext.cs

See Also​

Keywords​

  • Workforce Scheduling database
  • Shift persistence
  • Attendance policy storage

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Next review: 2026-10-20