Thanks for the clarification.
I understand that this is the intended behavior, and I can see why many users prefer it because it keeps editing quick and efficient.
The reason I brought up the suggestion is that, when working with important data, it's easy to click into another row by mistake and have a change submitted unintentionally. An optional setting that requires an explicit save/confirm action before committing changes could provide an extra layer of safety without changing the default workflow.
Regarding your suggestion to revoke INSERT/UPDATE/DELETE privileges, that can certainly help prevent accidental writes. However, it also prevents legitimate edits, so it addresses a slightly different use case. My suggestion is aimed at users who do need write access but would prefer an additional safeguard against unintended changes.
Some database tools take a similar approach by keeping changes pending until the user explicitly applies them. Having this as an optional preference could offer the best of both worlds: the current fast workflow for those who prefer it, and a more cautious workflow for environments where data integrity is especially important.
Just a suggestion for consideration, and thanks again for the response.