2

There is nothing wrong in having tables with no relationships. The choice of a database in order to store those settings is perfectly fine and quite common. The only issue you might encounter is performance, but basic caching at server level would quickly solve this. A usual problem is what types of columns should you use for such table if you're relying ...


1

Consider to implement a more declarative approach for validate_settings. You wrote Still, I can't think of a better way other than checking each individual key in each individual dictionay/subdictionary, since each key has a different name, each subdict has a different structure and many different data types are used for values. I can think of one. I ...


1

You don't have to test every value, as you're not testing the actual config. You're just testing the one "unit" which is the validate_settings method. Running this test won't tell you if your settings file is good, but it does tell you that you won't be able to start the program if your settings file is not good. You haven't shared the code for ...


Only top voted, non community-wiki answers of a minimum length are eligible