3.

The dirty read problem occurs often when a transaction is performed to read data, which is still being
modified by an other transaction.

If the truncation which is changing the data commits itself the dirty read problem will not happen. If the
read transaction happens before the modifying transaction is rolled back, the next transaction will have
dirty data that do not exist.

3.3

non-repeatable read occurs when the same data is read twice in the same transaction, but the data will not
occur as the same. It is often because the data has been changed, by an other transaction, in the time
between the reads. It can because of a change in the data or straight up by deleting the data.

Non-repeatable read occurs often when the isolation

3.4

The phantom read occurs when a transaction executes the same query more than one time, which results
in the rows made by the second transaction will not be visible for the first transactions result.

It happens when transaction adds new rows in between the execution of two queries. It is quiet similar to
the non-repeatable read. I different form the non-repeatable read is the number of rows is changed by
insertion or deletion.