# 
# 
# patch "database.cc"
#  from [179faaff204578919e180494b84614f6fd8a31a9]
#    to [95b2352645a231b30b7b923b7798ed0143f8c2f8]
# 
# patch "schema_migration.cc"
#  from [1354bd78efb75e321287e7f73b2a1b90805325e1]
#    to [a72f32cf9f51c6089d8a46f91703058b8d50aae7]
# 
============================================================
--- database.cc	179faaff204578919e180494b84614f6fd8a31a9
+++ database.cc	95b2352645a231b30b7b923b7798ed0143f8c2f8
@@ -75,7 +75,7 @@
   // non-alphabetic ordering of tables in sql source files. we could create
   // a temporary db, write our intended schema into it, and read it back,
   // but this seems like it would be too rude. possibly revisit this issue.
-  schema("1db80c7cee8fa966913db1a463ed50bf1b0e5b0e"),
+  schema("9d2b5d7b86df00c30ac34fe87a3c20f1195bb2df"),
   __sql(NULL),
   transaction_level(0)
 {}
============================================================
--- schema_migration.cc	1354bd78efb75e321287e7f73b2a1b90805325e1
+++ schema_migration.cc	a72f32cf9f51c6089d8a46f91703058b8d50aae7
@@ -1031,9 +1031,12 @@
   m.add("bd86f9a90b5d552f0be1fa9aee847ea0f317778b",
         &migrate_client_to_add_rosters);
 
+  m.add("1db80c7cee8fa966913db1a463ed50bf1b0e5b0e",
+        &migrate_files_BLOB);
+
   // IMPORTANT: whenever you modify this to add a new schema version, you must
   // also add a new migration test for the new schema version.  See
   // tests/t_migrate_schema.at for details.
 
-  m.migrate(sql, "1db80c7cee8fa966913db1a463ed50bf1b0e5b0e");
+  m.migrate(sql, "9d2b5d7b86df00c30ac34fe87a3c20f1195bb2df");
 }