Now that we accept a list of SQL statements to be executed individually (and

committed after each statement), I no longer need to manually handle table
population.
This commit is contained in:
Michael Bayne
2011-02-18 18:25:34 +00:00
parent 687de42168
commit 86476b4494
@@ -47,7 +47,6 @@ public class MigrationTest extends TestBase
public void testPKMigration () public void testPKMigration ()
{ {
PersistenceContext pctx = createPersistenceContext("pkmig", PK_DUMP); PersistenceContext pctx = createPersistenceContext("pkmig", PK_DUMP);
executeSQL(pctx, PK_INIT); // now that the schema is created, we can populate
DepotRepository repo = createRepository(pctx, PKMigrationRecord.class); DepotRepository repo = createRepository(pctx, PKMigrationRecord.class);
// trigger the execution of the migrations // trigger the execution of the migrations
pctx.initializeRepositories(true); pctx.initializeRepositories(true);
@@ -101,13 +100,12 @@ public class MigrationTest extends TestBase
"\"stringId\" VARCHAR(255) NOT NULL," + "\"stringId\" VARCHAR(255) NOT NULL," +
"PRIMARY KEY(\"id\",\"stringId\"))", "PRIMARY KEY(\"id\",\"stringId\"))",
"INSERT INTO \"DepotSchemaVersion\" VALUES('MigrationTest$PKMigrationRecord',1,0)" "INSERT INTO \"DepotSchemaVersion\" VALUES('MigrationTest$PKMigrationRecord',1,0)",
};
protected static final String PK_INIT =
"INSERT INTO \"MigrationTest$PKMigrationRecord\" VALUES(1,'1')\n" + "INSERT INTO \"MigrationTest$PKMigrationRecord\" VALUES(1,'1')\n" +
"INSERT INTO \"MigrationTest$PKMigrationRecord\" VALUES(2,'2')\n" + "INSERT INTO \"MigrationTest$PKMigrationRecord\" VALUES(2,'2')\n" +
"INSERT INTO \"MigrationTest$PKMigrationRecord\" VALUES(3,'3')\n" + "INSERT INTO \"MigrationTest$PKMigrationRecord\" VALUES(3,'3')\n" +
"INSERT INTO \"MigrationTest$PKMigrationRecord\" VALUES(4,'4')\n" + "INSERT INTO \"MigrationTest$PKMigrationRecord\" VALUES(4,'4')\n" +
"INSERT INTO \"MigrationTest$PKMigrationRecord\" VALUES(5,'5')\n"; "INSERT INTO \"MigrationTest$PKMigrationRecord\" VALUES(5,'5')\n"
};
} }