[TYPO3-dev] TYPO3 4.1 INNODB

Steffen Kamper steffen at dislabs.de
Sat Mar 3 11:07:40 CET 2007


"Martin Kutschker" <martin.kutschker-n0spam at no5pam-blackbox.net> schrieb im 
Newsbeitrag 
news:mailman.1.1172915234.19266.typo3-dev at lists.netfielders.de...
> R. van Twisk schrieb:
>>
>> Of course, if you look deep in my hart then I you will see that DBAL is a 
>> lot of work that gains not to much, but gave a nice interface for DB 
>> access. It's feature rich, but I think not to many ppl will use it.
>
> If you mean that only a few customers insist on using some other RDMBS 
> rather than Mysql I think you are right.
>
>> And I feel that specially in  this case
>> we should serve the mysql ppl and give them the full speed whenever 
>> possible for the used DB.
>
> DB tuning across multiple DB sytestems is like optimizing graphics 
> acceleration for multiple chip sets. You have to do do it for each chip 
> set.
>
> But going back to a Mysql-only application is IMHO a step back. I want 
> every customer not just the Mysql users. *
>
> Masi
>
>
> * And I do care about Windows servers, IIS, IE ;-)

Hi Masi,

you're absolutely right. But i like the idea of Ries to implement a tuning 
set for each DB System.
DBAL is the right place to do this. The problem will be, that no developer 
knows each model quite well.
So we have to think about a good solution. May be this could be done with a 
hook, so the optimizing could be done in a extra extension for each DB 
system. This will keep DBAL as a common interface and besides MySQL-Opt, 
Oracle-Opt, MSSQL-Opt etc.

vg  Steffen 






More information about the TYPO3-dev mailing list