/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 

    

  1. test10 README
    2. 

  2. =========
    3. 

  3. 

  4. Description
    5. 

  5. ----------
    6. 

  6. Compare two DB tables using mostly automatic default provided by the MagicPlan. Plan specifies keyColumnNames, 
    7. 

  7. which are different from the pk defined in the database for the target table. If alignment was carried out using 
    8. 

  8. table pk (column1), all rows would be row diffs. Instead, engine is able to align the rows and produce only column diffs
    9. 

  9. because of the keyColumnName override (column3).
    10. 

  10. 

  11. 

  12. Assumptions
    13. 

  13. -----------
    14. 

  14. - lhs & rhs are DB tables
    15. 

  15. - lhs vs. rhs has only column diffs
    16. 

  16. - plan file supplies lhs table name and rhs table name
    17. 

  17. - plan file supplies ConnectionInfo to H2 DB
    18. 

  18. - lhs and rhs tables have identical structure
    19. 

  19. - MagicPlan reverse engineers TableModels from the database
    20. 

  20. - MagicPlan generates default TableComparison by aligning lhs column to rhs column based on name
    21. 

  21. - MagicPlan uses COLUMN 3 as the key for both tables. This overrides the definition in the DB (column1).
    22. 

  22. 

  23. 

  24. Expectations
    25. 

  25. -----------
    26. 

  26. - 7 column diffs
    27.