[TYPO3-dev] sysext's

[ries van Twisk]

On Mar 22, 2008, at 9:05 AM, Oliver Hader wrote:

> Hi Dmitry,
>
> Dmitry Dulepov [typo3] schrieb:
>> Moreno Feltscher wrote:
>>> Once again (in the correct list) :-)
>>>
>>> -1 for removing DBAL as well, otherwise please change this:  
>>> Database:
>>> MySQL or any other database system supported by the TYPO3 DBAL (e.g.
>>> Oracle, Postgres and a lot of others) on
>>> http://typo3.org/about/system-requirements/
>>>
>>> If you also want to stay attractive to business companies, which  
>>> also
>>> are able to spend money to the assocation for developing the core,
>>> please keep in mind that many of them use enterprise database
>>> solutions as Oracle or MSSQL.
>>
>> Such companies stay with Oracle or MSSQL just because they spent time
>> and huge money training their people for these databases. But this is
>> not a problem of TYPO3. TYPO3 default database is MySQL and it is a
>> requirement. If company wants to use TYPO3 with other database, it  
>> has
>> to be ready for glitches, problems, etc. No one ever promised that  
>> TYPO3
>> will work with other databases as well as with MySQL. There is some
>> support but I see no reason to supply DBAL for everyone if only 1%  
>> uses
>> it. That big fat 1% can load DBAL from TER, no big deal.
>
> I always thought it's the other way round... ;-)
> Oracle has much more performance than MySQL (if you think about  
> advanced
> queues and putting your business logic inside the DBMS). But I agree,
> running the TYPO3 Core on Oracle isn't a good idea - but it happens,
> that DBAL is used to integrate e.g. a products database into the TYPO3
> system which is based on Oracle.
>
> I'm fine with removing DBAL from the Core (in 4.3), but someone has to
> take care about that extension - version "conflicts" have to be  
> avoided
> as well then.
>
> olly
> -- 
> Oliver Hader
> TYPO3 Core Team
> _______________________________________________
>

It's also (like in my case) that we have a other database to maintain,
  to backup, know to restore, to learn, to know it's tricks and flaws,
to learn how it's security works etc.. etc... That's also one of the  
reasons
why companies like to stick with there DB they know best...

Ries