PageRenderTime 30ms CodeModel.GetById 28ms app.highlight 1ms RepoModel.GetById 1ms app.codeStats 0ms

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

http://diffkit.googlecode.com/
Plain Text | 26 lines | 21 code | 5 blank | 0 comment | 0 complexity | 10d79b5e583ed7cf21833b6c295dfc2d MD5 | raw file
 1test11 README
 2=========
 3
 4Description
 5----------
 6Compare two file tables using mostly automatic default provided by the MagicPlan. Plan specifies keyColumnNames, 
 7which are different from the default pk (first column) for file based tables. If alignment was carried out using 
 8default 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 FILE tables
15- lhs vs. rhs has only column diffs
16- plan file supplies lhs table  and rhs table file paths
17- plan file supplies file path for Sink
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 default definition for FILE sources
22
23
24Expectations
25-----------
26- 7 column diffs