Bjoern Michaelsen 53e7011084 be picky and check explicit implementation name ...

- the previous code tried to avoid breakage from changing an
  implementation detail
- this turns out to be harder than expected in a Python2/3 portable way
- also it would mean the intentional drive-by documentation of the
  expected implementation name will at least not bit rot now

Change-Id: I5972d0e79ef64abe30573182c5e23268e4830ade

2015-07-03 22:12:57 +02:00

..

check_fields.py

…

check_index.py

…

check_table.py

be picky and check explicit implementation name

2015-07-03 22:12:57 +02:00

get_expression.py

…

set_expression.py

…

var_fields.py

…