[Monotone-commits-diffs] net.venge.monotone: 1e0674b7b7048041bc8219bc8838aaa57305b017

[code]

revision:            1e0674b7b7048041bc8219bc8838aaa57305b017
date:                2011-03-10T19:07:44
author:              Richard Levitte <address@hidden>
branch:              net.venge.monotone
changelog:
* test/func/schema_migration_new_db/__driver__.lua: Test that 'db
  migrate' really doesn't do more than necessary.  We try this on a fresh
  database.
* test/func/schema_migration_new_db/expected-stderr.txt: The expected
  output on stderr.

manifest:
format_version "1"

new_manifest [39e106f770110ca16639aef46a047caf39e1cb50]

old_revision [d48ba47d9712056855296371791c608aa9610852]

add_dir "test/func/schema_migration_new_db"

add_file "test/func/schema_migration_new_db/__driver__.lua"
 content [b1ed03f18f2480f322746b2e142f21ad005ae9cf]

add_file "test/func/schema_migration_new_db/expected-stderr.txt"
 content [f005e35ac5b31b7b8cf949037a871f4e0c52f6d8]
============================================================
--- /dev/null	
+++ test/func/schema_migration_new_db/__driver__.lua	b1ed03f18f2480f322746b2e142f21ad005ae9cf
@@ -0,0 +1,12 @@
+-- This is a very quick test to see that db migrate doesn't do more
+-- than it should.  The reason for this test is that mtn version 0.99
+-- would regenerate certain caches even when they were freshly regenerated.
+--
+-- The easiest way to check this is on a newly created database, which
+-- mtn_setup() kindly provides.
+
+mtn_setup()
+
+check(get("expected-stderr.txt"))
+check(mtn("db", "migrate"), 0, false, true)
+check(samefile("stderr", "expected-stderr.txt"))
============================================================
--- /dev/null	
+++ test/func/schema_migration_new_db/expected-stderr.txt	f005e35ac5b31b7b8cf949037a871f4e0c52f6d8
@@ -0,0 +1,2 @@
+mtn: calculating migration...
+mtn: no migration performed; database schema already up-to-date