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

Steffen Kamper info at sk-typo3.de
Mon Mar 7 15:32:11 CET 2011


Hi,

Am 07.03.2011 15:28, schrieb Dmitry Dulepov:
> Hi!
>
> Jigal van Hemert wrote:
>> TYPO3 only modifies database structures in a few situations: extension
>> manager and install tool. These functions (expanded by DBAL) could store
>> info about engine / DBMS somewhere in the system.
>
> They could. But why this is necessary? What would you achieve but this
> knowledge? :) Would you really check that in your code and do operations
> differently?
>
> Noprmally you expect that the database is set up as a developer
> suggested (i.e. use InnoDB for certain tables). You would use
> transactions in the code. If somebody did not use InnoDB, it is not the
> fault of the developer and he should not care about it. It is simply
> improper database set up and all responsibility lies on the [bad] admin.
>

i agree. It's not on the developer to take care, it's up to the API to 
do the correct things.

btw - seems bad admins all around, i often see problems with not 
existing innoDB, crashing innoDB tables etc. It seems not so easy to 
seperate innoDB to not getting a monster file where you can't shrink it.

vg Steffen




More information about the TYPO3-dev mailing list