add-ideas/govoplan-core
1
0
Fork 0
Code Issues 45 Pull Requests Actions Packages Projects Releases Wiki Activity

[Task] Decide: Which table names must remain stable for painless migrations? #55

New Issue
Closed
opened 2026-07-06 11:34:38 +02:00 by zemion · 2 comments
zemion commented 2026-07-06 11:34:38 +02:00
Owner
Copy Link

Imported from the GovOPlaN access extraction plan open decisions.

  • Source: /mnt/DATA/git/govoplan-core/docs/ACCESS_EXTRACTION_PLAN.md
  • Line: 356
  • Section: Open Decisions
  • Source status: decision needed

Imported backlog item:

- [ ] Which table names must remain stable for painless migrations?
<!-- codex-backlog-fingerprint:b79321c1ea721a21c3cdf68c --> Imported from the GovOPlaN access extraction plan open decisions. - Source: `/mnt/DATA/git/govoplan-core/docs/ACCESS_EXTRACTION_PLAN.md` - Line: `356` - Section: `Open Decisions` - Source status: `decision needed` Imported backlog item: ```markdown - [ ] Which table names must remain stable for painless migrations? ```
zemion added this to the Access Extraction milestone 2026-07-06 12:48:57 +02:00
zemion added the
status
needs-info
 label 2026-07-08 03:00:06 +02:00
zemion commented 2026-07-09 10:31:06 +02:00
Author
Owner
Copy Link

Codex State: recommendation 2026-07-09

Recommendation: keep the historical live table names stable as the migration contract, and close this once accepted.

Suggested decision:

  • Preserve existing persisted table names for painless upgrades: accounts, users, groups, roles, api_keys, auth_sessions, tenants, system_settings, governance_templates, governance_template_assignments, audit_log, mail_server_profiles, file_connector_profiles, and file_connector_credentials.
  • Do not rename migrated tables to module-prefixed alternatives such as access_users unless an explicit data migration and compatibility window is approved.
  • New module-owned tables should use clear module-owned names from the start.
  • Module ownership may move, but table names are part of the persistence ABI.

Effects: this keeps #43 closed, constrains #62/#63 cleanup to code ownership rather than table renames, and keeps #82 focused on tenant lifecycle/switching/deletion rather than tenant table renaming.

## Codex State: recommendation 2026-07-09 Recommendation: keep the historical live table names stable as the migration contract, and close this once accepted. Suggested decision: - Preserve existing persisted table names for painless upgrades: accounts, users, groups, roles, api_keys, auth_sessions, tenants, system_settings, governance_templates, governance_template_assignments, audit_log, mail_server_profiles, file_connector_profiles, and file_connector_credentials. - Do not rename migrated tables to module-prefixed alternatives such as access_users unless an explicit data migration and compatibility window is approved. - New module-owned tables should use clear module-owned names from the start. - Module ownership may move, but table names are part of the persistence ABI. Effects: this keeps #43 closed, constrains #62/#63 cleanup to code ownership rather than table renames, and keeps #82 focused on tenant lifecycle/switching/deletion rather than tenant table renaming.
zemion commented 2026-07-09 11:00:57 +02:00
Author
Owner
Copy Link

Implemented the early-development table namespace cleanup.

Summary:

  • Renamed core/access/tenancy/admin-owned platform tables to module-scoped names such as access_users, access_groups, access_roles, access_api_keys, tenancy_tenants, core_system_settings, and admin_governance_templates.
  • Updated ORM models, foreign keys, indexes, live module migrations, reconciliation checks, and tests to use the new names.
  • Added compatibility migration 2e3f4a5b6c7d_namespace_platform_tables.py to rename existing early-dev databases, while fresh databases create the names directly.
  • Kept already module-scoped tables such as mail_, file_, calendar_, campaign, and audit_log unchanged.

Verification passed:

  • python -m unittest tests.test_database_migrations
  • python -m unittest tests.test_module_system tests.test_access_contracts
  • python -m compileall over core/access/tenancy/admin/audit/mail/files/campaign/calendar packages
  • scripts/check_dependency_boundaries.py
  • npm run test:module-permutations

Closing this because the decision has been made and the rename is implemented.

Implemented the early-development table namespace cleanup. Summary: - Renamed core/access/tenancy/admin-owned platform tables to module-scoped names such as access_users, access_groups, access_roles, access_api_keys, tenancy_tenants, core_system_settings, and admin_governance_templates. - Updated ORM models, foreign keys, indexes, live module migrations, reconciliation checks, and tests to use the new names. - Added compatibility migration 2e3f4a5b6c7d_namespace_platform_tables.py to rename existing early-dev databases, while fresh databases create the names directly. - Kept already module-scoped tables such as mail_*, file_*, calendar_*, campaign*, and audit_log unchanged. Verification passed: - python -m unittest tests.test_database_migrations - python -m unittest tests.test_module_system tests.test_access_contracts - python -m compileall over core/access/tenancy/admin/audit/mail/files/campaign/calendar packages - scripts/check_dependency_boundaries.py - npm run test:module-permutations Closing this because the decision has been made and the rename is implemented.
zemion removed the
codex/needs-human
status
needs-info
 labels 2026-07-09 11:00:58 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
HTTP API contracts, routers, schemas, or API smoke behavior.
area/auth
Authentication, sessions, access bootstrap, or login behavior.
area/db
Database sessions, models, transactions, or persistence primitives.
area/deployment
Deployment, release, operations, or runtime packaging.
area/devex
Local developer workflow, scripts, tests, tooling, or release helpers.
area/docs
Durable documentation and project guidance.
area/governance
Governance policy, audit, privacy, retention, or compliance behavior.
area/marketing
Public website, product messaging, publication copy, or legal page content.
area/migrations
Alembic migrations, schema bootstrap, or persistence evolution.
area/module-system
Module discovery, manifests, capabilities, routing, or optional integrations.
area/rbac
Permissions, roles, delegation, or authorization policy.
area/release
Versioning, release locks, tags, packaging, or dependency pins.
area/security
Security posture, static analysis, supply-chain hardening, or vulnerability remediation.
area/tenancy
Tenant boundaries, provisioning, or tenant-scoped data behavior.
area/webui
Shared WebUI shell, frontend components, routing, or frontend tests.
audit/complexity
Complexity finding from Radon, Xenon, or equivalent maintainability scans.
audit/duplication
Duplicated-code finding from jscpd or equivalent similarity scans.
audit/false-positive
Audit finding reviewed as a narrow false positive or acceptable risk.
audit/needs-design
Audit finding that needs an architectural or product decision before implementation.
audit/quick-fix
Audit finding that appears narrow and directly fixable.
audit/structural
Audit finding that needs design, refactoring, or behavior review.
codex/needs-human
Needs an explicit human decision before Codex should implement.
codex/ready
Suitable for Codex to pick up with the existing issue context.
module/access
GovOPlaN access, identity, authentication, RBAC, and administration behavior.
module/addresses
GovOPlaN Addresses module behavior or integration.
module/admin
GovOPlaN Admin module behavior or integration.
module/appointments
GovOPlaN Appointments module behavior or integration.
module/approvals
GovOPlaN Approvals module behavior or integration.
module/assets
GovOPlaN Assets module behavior or integration.
module/audit
GovOPlaN Audit module behavior or integration.
module/booking
GovOPlaN Booking module behavior or integration.
module/calendar
GovOPlaN Calendar module behavior or integration.
module/campaign
GovOPlaN campaign module behavior or integration.
module/cases
GovOPlaN Cases module behavior or integration.
module/certificates
GovOPlaN Certificates module behavior or integration.
module/committee
GovOPlaN Committee module behavior or integration.
module/connectors
GovOPlaN Connectors module behavior or integration.
module/consultation
GovOPlaN Consultation module behavior or integration.
module/contracts
GovOPlaN Contracts module behavior or integration.
module/core
GovOPlaN core runner, shared primitives, shell, or extension points.
module/dist-lists
GovOPlaN Distribution Lists module behavior or integration.
module/dms
GovOPlaN Dms module behavior or integration.
module/docs
GovOPlaN documentation layer behavior or integration.
module/erp
GovOPlaN Erp module behavior or integration.
module/evaluation
GovOPlaN Evaluation module behavior or integration.
module/facilities
GovOPlaN Facilities module behavior or integration.
module/files
GovOPlaN files module behavior or integration.
module/fit-connect
GovOPlaN Fit Connect module behavior or integration.
module/forms
GovOPlaN Forms module behavior or integration.
module/forms-runtime
GovOPlaN Forms Runtime module behavior or integration.
module/grants
GovOPlaN Grants module behavior or integration.
module/helpdesk
GovOPlaN Helpdesk module behavior or integration.
module/identity
GovOPlaN Identity module behavior or integration.
module/identity-trust
GovOPlaN Identity Trust module behavior or integration.
module/idm
GovOPlaN Idm module behavior or integration.
module/inspections
GovOPlaN Inspections module behavior or integration.
module/issue-reporting
GovOPlaN Issue Reporting module behavior or integration.
module/learning
GovOPlaN Learning module behavior or integration.
module/ledger
GovOPlaN Ledger module behavior or integration.
module/mail
GovOPlaN mail module behavior or integration.
module/notifications
GovOPlaN Notifications module behavior or integration.
module/ops
GovOPlaN Ops module behavior or integration.
module/organizations
GovOPlaN Organizations module behavior or integration.
module/payments
GovOPlaN Payments module behavior or integration.
module/permits
GovOPlaN Permits module behavior or integration.
module/policy
GovOPlaN Policy module behavior or integration.
module/poll
GovOPlaN Poll module behavior or integration.
module/portal
GovOPlaN Portal module behavior or integration.
module/postbox
GovOPlaN Postbox module behavior or integration.
module/procurement
GovOPlaN Procurement module behavior or integration.
module/records
GovOPlaN Records module behavior or integration.
module/reporting
GovOPlaN Reporting module behavior or integration.
module/resources
GovOPlaN Resources module behavior or integration.
module/risk-compliance
GovOPlaN Risk Compliance module behavior or integration.
module/scheduling
GovOPlaN Scheduling module behavior or integration.
module/search
GovOPlaN Search module behavior or integration.
module/tasks
GovOPlaN Tasks module behavior or integration.
module/templates
GovOPlaN Templates module behavior or integration.
module/tenancy
GovOPlaN Tenancy module behavior or integration.
module/transparency
GovOPlaN Transparency module behavior or integration.
module/web
GovOPlaN public website, product page, or publication content.
module/workflow
GovOPlaN Workflow module behavior or integration.
module/xoev
GovOPlaN Xoev module behavior or integration.
module/xrechnung
GovOPlaN Xrechnung module behavior or integration.
module/xta-osci
GovOPlaN Xta Osci module behavior or integration.
priority
p0
Immediate stop-the-line priority.
priority
p1
High priority for the next focused work window.
priority
p2
Normal planned priority.
priority
p3
Low priority or opportunistic cleanup.
source/backlog-import
Imported from markdown backlog, roadmap, plan, or TODO files.
source/module-roadmap
Created from GovOPlaN module and integration roadmap planning.
source/security-audit
Created from a structured security or code-quality audit report.
source/todo-scan
Imported from inline TODO/FIXME/HACK markers by the Gitea TODO importer.
status
blocked
Cannot progress without a decision, dependency, credential, or external change.
status
in-progress
Currently being worked.
status
needs-info
Needs clarifying input before implementation can proceed safely.
status
ready
Ready for implementation.
status
triage
Needs review, ownership, priority, or acceptance criteria.
type
bug
A reproducible defect, regression, or incorrect behavior.
type
debt
Cleanup, refactoring, risk reduction, or deferred engineering work.
type
docs
Documentation, process, or developer workflow work.
type
feature
New user-visible behavior or platform capability.
type
task
Implementation, maintenance, migration, or operational work.
type
user-story
End-to-end user journey or real-world process story used to steer product slices.
No Label
area/auth
codex/ready
module/access
module/core
priority
p1
source/backlog-import
type
task
Milestone
No items
No Milestone Access Extraction
Projects
Clear projects
No project
Assignees
Clear assignees
zemion
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-core#55
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?