IntegerMigrator doesn't allow duplicate migrations (1_foo, 1_bar). Requires manual renaming for simultaneous migrations. Here's comparison in detail: https://sequel.jeremyevans.net/rdoc/files/doc/migration_rdoc.html#label-Two+separate+migrators The TimestampMigrator will be used if any filename in the migrations directory has a version greater than 20000101. IntegerMigrator keeps version information at scheme_info table with an integer. But TimestampMigrator keeps version information at scheme_migrations tables with all filenames. It's not backward compatible. You need to reset your database or create and fill scheme_migrations table manually, then drop scheme_info table.
19 lines
525 B
Ruby
19 lines
525 B
Ruby
# frozen_string_literal: true
|
|
|
|
Sequel.migration do
|
|
change do
|
|
alter_table(:vm_host) do
|
|
add_column :total_mem_gib, Integer
|
|
|
|
# Standardize on lscpu nomenclature. "cpus" may also be
|
|
# "threads," "nodes" seems to closest to "dies." "Socket" could
|
|
# also be rendered "package." "core" has no terminological
|
|
# variants.
|
|
add_column :total_sockets, Integer
|
|
add_column :total_nodes, Integer
|
|
add_column :total_cores, Integer
|
|
add_column :total_cpus, Integer
|
|
end
|
|
end
|
|
end
|