[TYPO3-dev] malformed cached config files

[Xavier Perseguers]

Hi,

> I decided to use transactions which, at least in MySQL, provides all we
> need to implement a read/write lock. Sadly t3lib_DB does not support
> transactions. Even "worse" it uses pconnect which does not work in
> conjunction with transactions. So I open a new connection for each

You can and should actually deactivate it with a configuration setting...

> instance. I tested it and it worked just fine for me. It also seems to
> be faster than the filebased locking method.
>
> There is just one problem ... I do not delete the "lock records" I do
> the blocking SELECTs on. Deleting old records would make parallel read
> locks impossible on those records.
>
> Ok, so how are the chances to get something like that into the core?
> If there's any, I will post it as reply to the issue #18557.

If you want to add support for transactions, you should make sure it can 
be compatible with the use of DBAL. But I'm quite sure we could do 
something there as well.

Cheers

-- 
Xavier Perseguers
Release Manager TYPO3 4.6

TYPO3 .... inspiring people to share!
Get involved: http://typo3.org