Use real timestamp IDs for resource allocation migrations

Browse Source

The migrations used a date plus a fake incrementing hour counter
(e.g. 20260602120000, ...130000, ...140000) rather than real
timestamps. Those synthetic IDs risk colliding with migrations added
elsewhere in the app. Rename them to their actual file creation time:

  20260602120000 -> 20260602152805  add_users
  20260602130000 -> 20260602152807  create_..._journals
  20260602140000 -> 20260602170908  add_filter_name

create_resource_allocations already had a real timestamp and is left
unchanged. Order and resulting schema are preserved.

...

This commit is contained in:

Klaus Zanders

2026-06-03 11:43:29 +02:00

parent 3466daba5e

commit 323c095e36

3 changed files with 0 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

modules/resource_management/db/migrate/20260602120000_add_users_to_resource_allocations.rb → modules/resource_management/db/migrate/20260602152805_add_users_to_resource_allocations.rb

modules/resource_management/db/migrate/20260602130000_create_resource_allocation_journals.rb → modules/resource_management/db/migrate/20260602152807_create_resource_allocation_journals.rb

modules/resource_management/db/migrate/20260602140000_add_filter_name_to_resource_allocations.rb → modules/resource_management/db/migrate/20260602170908_add_filter_name_to_resource_allocations.rb