# 
# 
# patch "database.cc"
#  from [b3e5c5859ebb6dd165ce8bf52d98908b6d737ede]
#    to [782fe442be38102309140cac08d6d9f304cc233b]
# 
# patch "schema_migration.cc"
#  from [a15f0fb822c1ec4c500e1f12d279bf62931e2a16]
#    to [bf93c9946d91eb904ce2fe89a85bf50a60687c67]
# 
============================================================
--- database.cc	b3e5c5859ebb6dd165ce8bf52d98908b6d737ede
+++ database.cc	782fe442be38102309140cac08d6d9f304cc233b
@@ -72,7 +72,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("d19b106aaabbf31c89420a27224766eab10b6783"),
+  schema("2d7ffb7c3d2975b52d2c799d511b7aea196c7adf"),
   __sql(NULL),
   transaction_level(0)
 {}
============================================================
--- schema_migration.cc	a15f0fb822c1ec4c500e1f12d279bf62931e2a16
+++ schema_migration.cc	bf93c9946d91eb904ce2fe89a85bf50a60687c67
@@ -1058,5 +1058,5 @@
   // also add a new migration test for the new schema version.  See
   // tests/t_migrate_schema.at for details.
 
-  m.migrate(sql, "d19b106aaabbf31c89420a27224766eab10b6783");
+  m.migrate(sql, "2d7ffb7c3d2975b52d2c799d511b7aea196c7adf");
 }