activerecord-virgodb-adapter 0.1.7 → 0.1.8

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d70a70ab0e46de3acd4d283c69e7c385873c7bb9ec817423f62ff09dbc601350
-  data.tar.gz: 1f7b6259306a3d61f2e3d05fb345373a5d350b2742309804be1d91ac096886a1
+  metadata.gz: b21e3613bde955c3741ba92692bb2465036783609e4d11f9540ce0283ea83732
+  data.tar.gz: 34b1d14f797d629a6f09c029d422803353df2d86cb8c0682883bbb90d56fde18
 SHA512:
-  metadata.gz: 64c5716aa1f9d1ea110aacd562ad131acb5d8d76bbd4e8d0ed459a2191530d7b27c6c1f924b59a70840defed6f285c668e6fc9a56f97b134719bd2033ed42b6f
-  data.tar.gz: 9f2de20a524c86e2bafc0a43b6f49b8d86bdf127a54b8a5276972f75b10e937c5c7fe3b89b88172eaca32b4aaee09aa0aa52a34f947c614dc3926c3d1878f82e
+  metadata.gz: cbafb03b4df28cc059ed39deffd6504916232cb545b4ae2c7bce66e55121837e90cb3a76c8ecc6fd074277665abd6c438042ecce57530a5960b0fc6391a2d314
+  data.tar.gz: 79aae8c9a8cbcc419ac83295f371d24122cfddf291d5974c473d23cbafa512b3a177109197b86f090c349af594eb1533d47bea3e2bd84e7a2a28fe835d08c02a

data/lib/active_record/tasks/virgodb_database_tasks.rb

@@ -134,32 +134,45 @@ module ActiveRecord
       # history here isn't a correctness requirement. It also isn't a
       # readability win: each version's `columns` re-lists every column from
       # scratch, so N migrations means N near-duplicate JSON blobs, longer
-      # every time. The version count/dates are still worth one line for
-      # orientation -- the full column list per version isn't; the
-      # migration files themselves (db/migrate_virgodb_*/*.rb, timestamped,
-      # under git blame) are already the authoritative "what changed when"
-      # record. `register_schema_version`'s additive-only check is
-      # unaffected: it only ever compares a new migration's proposed columns
-      # against the CURRENT version, which is exactly what's still dumped.
+      # every time. The migration files themselves (db/migrate_virgodb_*/*.rb,
+      # timestamped, under git blame) are already the authoritative "what
+      # changed when" record. `register_schema_version`'s additive-only check
+      # is unaffected: it only ever compares a new migration's proposed
+      # columns against the CURRENT version, which is exactly what's still
+      # dumped.
+      #
+      # `applied_at` is dumped as a fixed `0`, and no per-version history
+      # comment is written -- both used to carry real wall-clock data
+      # (`Time.now.to_i` at migration time), which made this file diff on
+      # every clean rebuild (`db:drop` + `db:migrate`) even when the actual
+      # schema hadn't changed at all. Confirmed nothing reads either back:
+      # `current_schema_version` only ever selects `version, columns` (see
+      # above), and this adapter's own `assert_additive!`/
+      # `record_added_column!` only ever read `columns` too. The live
+      # manifest's real `schema_versions` table is untouched by this --
+      # `applied_at` still gets a real timestamp there at migration time,
+      # useful for a human inspecting the live table directly. This only
+      # changes what a fresh `structure_load` seeds into a NEW database,
+      # where a wall-clock value was never reproducible enough to belong in
+      # a checked-in file meant to represent "current schema shape," not
+      # "when someone last regenerated this file."
       def dump_schema_versions!(filename)
         return unless connection.data_source_exists?("schema_versions")
 
-        rows = connection.select_all("SELECT id, table_name, version, columns, applied_at FROM schema_versions ORDER BY table_name, version")
+        rows = connection.select_all("SELECT id, table_name, version, columns FROM schema_versions ORDER BY table_name, version")
         return if rows.to_a.empty?
 
         File.open(filename, "a") do |f|
           f.puts
           rows.to_a.group_by { |r| r["table_name"] }.each do |table_name, versions|
             latest = versions.max_by { |r| r["version"] }
-            history = versions.map { |r| "v#{r['version']} (#{Time.at(r['applied_at'].to_i).utc.strftime('%Y-%m-%d')})" }.join(", ")
 
-            f.puts "-- #{table_name} schema history: #{history} -- only the current version is dumped below; see db/migrate_virgodb_*/ for the rest"
             pretty_columns = JSON.pretty_generate(JSON.parse(latest["columns"]))
             f.puts(
               "INSERT INTO \"schema_versions\" (id, table_name, version, columns, applied_at) VALUES (\n" \
               "  #{latest['id']}, #{connection.quote(table_name)}, #{latest['version']},\n" \
               "  #{connection.quote(pretty_columns)},\n" \
-              "  #{latest['applied_at']}\n" \
+              "  0\n" \
               ");"
             )
             f.puts
@@ -199,7 +212,7 @@ module ActiveRecord
       # `SQLiteDatabaseTasks#structure_dump`'s `ignore_tables`-triggered
       # fallback (used whenever `ActiveRecord::SchemaDumper.ignore_tables` is
       # non-empty, e.g. excluding tables owned by a separate replication/
-      # backup mechanism -- exactly hintpot's own litestream initializer)
+      # backup mechanism -- exactly a host app's own Litestream initializer)
       # runs `SELECT sql || ';' FROM sqlite_master WHERE tbl_name NOT IN
       # (...) ORDER BY tbl_name, type DESC, name` through the `sqlite3` CLI.
       # Any table with a non-INTEGER (so non-rowid-alias) PRIMARY KEY --
@@ -271,8 +284,8 @@ module ActiveRecord
 
       # Matches `db/clickhouse_structure.sql` and `db/schema.rb`'s own
       # convention (both, unprompted, separate every top-level table
-      # definition with a blank line -- confirmed directly against
-      # hintpot's real dumps of each, not assumed) rather than inventing a
+      # definition with a blank line -- confirmed directly against a real
+      # host app's dumps of each, not assumed) rather than inventing a
       # new one here. Only CREATE TABLE gets a leading blank line, not
       # CREATE INDEX/CREATE UNIQUE INDEX -- those stay glued directly under
       # their own table, same as clickhouse_structure.sql has no equivalent

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: activerecord-virgodb-adapter
 version: !ruby/object:Gem::Version
-  version: 0.1.7
+  version: 0.1.8
 platform: ruby
 authors:
 - virgodb