PageRenderTime 49ms CodeModel.GetById 45ms app.highlight 1ms RepoModel.GetById 2ms app.codeStats 0ms

/tst/org/diffkit/diff/testcase/test10.README.txt

http://diffkit.googlecode.com/
Plain Text | 26 lines | 21 code | 5 blank | 0 comment | 0 complexity | c4a59056a1f754690752b3e40627a80c MD5 | raw file
 1test10 README
 2=========
 3
 4Description
 5----------
 6Compare two DB tables using mostly automatic default provided by the MagicPlan. Plan specifies keyColumnNames, 
 7which are different from the pk defined in the database for the target table. If alignment was carried out using 
 8table pk (column1), all rows would be row diffs. Instead, engine is able to align the rows and produce only column diffs
 9because of the keyColumnName override (column3).
10
11
12Assumptions
13-----------
14- lhs & rhs are DB tables
15- lhs vs. rhs has only column diffs
16- plan file supplies lhs table name and rhs table name
17- plan file supplies ConnectionInfo to H2 DB
18- lhs and rhs tables have identical structure
19- MagicPlan reverse engineers TableModels from the database
20- MagicPlan generates default TableComparison by aligning lhs column to rhs column based on name
21- MagicPlan uses COLUMN 3 as the key for both tables. This overrides the definition in the DB (column1).
22
23
24Expectations
25-----------
26- 7 column diffs