fixing flaky manual tx handling in a unit test

without it , the test would freeze connection pull on MySQL
Squashed commit of the following:

commit 87769731d15f9a0e410278bf30270292efcf1227
Author: alexkolonitsky <Alex.Kolonitsky@gmail.com>
Date:   Fri Aug 29 12:58:50 2014 +0300

    fix compilation errors

commit d3b0f45d2ab23a65025ab770392d2bda0afe7a81
Author: alexkolonitsky <Alex.Kolonitsky@gmail.com>
Date:   Fri Aug 29 12:57:33 2014 +0300

    fix compilation errors

commit 013d4f2211248f973adba3c3b0541cc087be1ce0
Author: alexkolonitsky <Alex.Kolonitsky@gmail.com>
Date:   Fri Aug 29 12:36:22 2014 +0300

    1) make token name a constructor parameter and remove all other implementations of this method
    2) I've created builders for domain objects (i.e. DataMap, Db\Obj Entity, Db\Obj Attribute, ...) and Factory for all builders; Main goal to provide easy way of construction objects and fill them partially with only data that necessary for test case, everything else required to make object valid will be generated randomly.
    3) DbMergerTest - test correct identification of DbToModel changes
    4) TokensReversTest - test compliance with the invariant token.reverse.reverse == token
    5) TokensToModelExecution - test application correctness of DbToModel tokens
    6) new dependency datafactory - in order to use random data in tests where exact value not really important
typo in the test name