It’s more about usability and performance on the stacks editing page.
Yes, that might be how I am implementing it. But it involves the potential of more end user mistakes.
It’s more about usability and performance on the stacks editing page.
Yes, that might be how I am implementing it. But it involves the potential of more end user mistakes.
I would have thought that the issue would be more the Stacks interface and the “weight” of the Stacks page, than DB vs flat file.
I mentioned 10 as a value more than 2 really, without much detailed thought.
I think a numbered set of variables could be a good way forward and if there is room to add a Stacks setting description for each number, that could create an acceptable end user interface.