While this particular example might not be considered severe, other more malicious code could be added, especially DELETE or UPDATE statements that modify tables.
虽然这个特例的后果可能并不太严重,但完全有可能添加更恶意的代码,尤其是会修改表的DELETE或update语句。
It's not a technical issue, obviously, as programming a functionality to let users delete their own accounts is something most competent developers could do before breakfast.
这不是一个技术问题,显然,实现让用户删除自己的帐户的功能是许多程序开发者必须要做的事情。
What if you did something radical like delete your defect backlog, with the understanding that going forward not a single defect could cross an iteration boundary?
如果您做了一些极端的操作,比如删除缺陷日志,而且理解并不是单个缺陷可以通过迭代的界限?
应用推荐