[TYPO3-dev] Idea: add transaction support to t3lib_db

[Jigal van Hemert]

Hi,

On 7-3-2011 10:13, Dmitry Dulepov wrote:
> Jigal van Hemert wrote:
>> If you want to perform an operation which requires that the table
>> doesn't change between two queries you might want to decide to lock the
>> table
>
> Lock a table on a site for each user with 2000 users working on it at
> the same time??? The site will be dead immediately. Not a solution.

INSERT and UPDATE queries lock a table in many cases already with 
non-transactional engines. These locks don't take a long time, but it 
can slow down the system indeed.

What other solution do you have for a replacement for transactions? Just 
ignoring the fact that a transaction couldn't be started is conceptually 
wrong. If a second or third query depends on the situation of the table 
during the first query and you are using transactions for this, you 
could end up with incorrect data when you simply ignore whether a 
transaction could be started or not.

-- 
Kind regards / met vriendelijke groet,

Jigal van Hemert
skype:jigal.van.hemert
msn: jigal at xs4all.nl
http://twitter.com/jigalvh