avoid implicit commits

[dimitri-yatsenko]

MySQL performs implicit commits in some conditions https://dev.mysql.com/doc/refman/5.7/en/implicit-commit.html

This causes a problem in populate calls when the populated table or its subtable is used for the first time in a _make_tuples call.

This problem affects both the matlab and the python implementation.

The solution I see to this is to roll back the ongoing transaction before creating a table and throwing an error after the table is created, forcing the user to re-rerun the analysis. Is there a more elegant solution?

[dimitri-yatsenko]

This was solved by declaring table at class definition rather than instantiation in the decorator-based class-relation binding approach.