We are using
The default transaction isolation level of a Doctrine\DBAL\Connection is chosen by the underlying platform but it is always at least READ_COMMITTED.
This could result in unpredictable results because an explicit WITH (NOLOCK) table hint tells SQL Server to run a specific query in transaction isolation level READ UNCOMMITTED instead of the default READ COMMITTED transaction isolation level. Therefore there now is a distinction between LockMode::NONE and null to be able to tell Doctrine whether to add table lock hints to queries by intention or not.
MySqlthe default isolation level is
MSSqlthe default isolation level is
Unless you change the default setting of the middleware(ORM) the following statement is valid:
The default transaction isolation level of a Doctrine\DBAL\Connection is chosen by the underlying platform.