4 ms·
See my comment at https://news.ycombinator.com/item?id=40107325 https://news.ycombinator.com/item?id=40107325 for the use case. It is a safety feature that can
by btilly 3y ago
See my comment at https://news.ycombinator.com/item?id=40107325 https://news.ycombinator.com/item?id=40107325 for the use case.
It is a safety feature that can help avoid people getting confused when working in a containerized environment. It is not a security feature at all. Nor is it intended to be. It is meant so that people like me can set up a configuration that will work better for coworkers who know less about databases than I do.
- noodlesUK 3y agoThen surely the answer should be that there should be a config setting that disables it, with the option to do something like "WITH FORCE" which would force enable it in the environment even with that config setting enabled. This gives the best of both worlds, in that it stops people from copying blindly from Stack Overflow, but doesn't give the sense of security that it initially seems to imply.
- btilly 3y agoYes, lots of people had ideas about this should work. Exactly like you just did. Unfortunately they had different ideas. And that's why there was months of debate over how this feature should work before something was accepted. Just to give one example of an obvious problem with your idea, saying "WITH FORCE" will suggest to some that this configuration setting is somehow forcibly maintained. This is likely to generate bug reports based on that misunderstanding. "I said WITH FORCE and it is easy to get around!" And, worse yet, questions about, "Why do we have a security feature that doesn't provide any security?"