Final answer:
In database management systems, a transaction should not make its updates visible to other transactions until it is committed, which is known as the atomicity of transactions.
Step-by-step explanation:
The statement is true. In database management systems, a transaction should not make its updates visible to other transactions until it is committed. This property is known as the atomicity of transactions. When enforced strictly, it solves the temporary update problem and makes cascading rollbacks of transactions unnecessary.