DDC-2179: Transactions should sent in group not chunked #2742

New Issue

admin · 2026-01-22T14:02:08+01:00

admin commented

2026-01-22 14:02:08 +01:00

Originally created by @doctrinebot on GitHub (Nov 29, 2012).

Originally assigned to: @Ocramius on GitHub.

Jira issue originally created by user dlsniper:

In UnitOfWork::commit() it seems that a transaction is done like this:

will send separate queries for transaction start
compute the queries/send them to the db driver
execute the commit statement
optionally execute rollback

The question would be, should my webserver have some issues with resources, wouldn't this part of the code be a pain for the DB?

I don't know how mysql, for example, handles sending the transaction in chunks as opposed to sending it in 2/3 statements ( begin ops and commit / revert in case of failure) or in mySQL,l the transaction is evaluated on COMMIT statement only?

If my assumption about how MySQL works, locking everything as soon as the statement is on the server, then shouldn't Doctrine use a internal buffer for sending transactions to the DB driver in order to avoid all sorts of problems that appear in high concurency scenarios?

Best regards.

Originally created by @doctrinebot on GitHub (Nov 29, 2012). Originally assigned to: @Ocramius on GitHub. Jira issue originally created by user dlsniper: In UnitOfWork::commit() it seems that a transaction is done like this: - will send separate queries for transaction start - compute the queries/send them to the db driver - execute the commit statement - optionally execute rollback The question would be, should my webserver have some issues with resources, wouldn't this part of the code be a pain for the DB? I don't know how mysql, for example, handles sending the transaction in chunks as opposed to sending it in 2/3 statements ( begin <ins> ops and commit / </ins> revert in case of failure) or in mySQL,l the transaction is evaluated on COMMIT statement only? If my assumption about how MySQL works, locking everything as soon as the statement is on the server, then shouldn't Doctrine use a internal buffer for sending transactions to the DB driver in order to avoid all sorts of problems that appear in high concurency scenarios? Best regards.

admin added the Bug label 2026-01-22 14:02:08 +01:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: doctrine/archived-orm#2742