In re: #250
Match each table to at most one config section
- filter duplicate table entries out of table_names in get_tables_and_gsis()
- use collections.OrderedDict to preserve the order of table
configuration sections as we parse the config file
- use ordereddict from PyPi if we are using python < 2.7
leave off ordereddict if >=2.7
@memory Thanks for your contribution. I think this makes sense. The problem for me is that it's breaking backwards compatibility (as some users current configuration will behave diffrently when this PR is merged).
My strategy for version numbers is that x.y.z:
This would thus be an update to x meaning it would be part of dynamic-dynamodb version 2. No problem per se, but I want to wait with merging this until we can do a proper v2 release with the changes mentioned in #252.
That seems valid -- it would definitely potentially break existing configurations. I will hold my breath for v2.0.0. :)