Damien Elmes 676f4e74a8 store config in separate DB table ... - mtime is tracked on each key individually, which will allow merging of config changes when syncing in the future - added col.(get|set|remove)_config() - in order to support existing code that was mutating returned values (eg col.conf["something"]["another"] = 5), the returned list/dict will be automatically wrapped so that when the value is dropped, it will save the mutated item back to the DB if it's changed. Code that is fetching lists/dicts from the config like so: col.conf["foo"]["bar"] = baz col.setMod() will continue to work in most case, but should be gradually updated to: conf = col.get_config("foo") conf["bar"] = baz col.set_config("foo", conf)		2020-04-06 15:39:47 +10:00
..
.gitignore	rework Fluent handling	2020-02-23 13:22:50 +10:00
backend.proto	store config in separate DB table	2020-04-06 15:39:47 +10:00