[Typo3-dev] DBAL - how to do it?

Mathias Schreiber [K1net] ms at k1net.de
Mon Feb 16 09:20:05 CET 2004


Kasper Skårhøj wrote:
> Then they don't deserve TYPO3 anyways. I'm not afraid of loosing
> "customers" on that account.

I think DBA might be priorized as B or C.
As soon as we talk about the pricerange of an Oracle or a MSSQL Server we
are talking about dedicated machines anyways.
To me, DBA is more about being able to cluster machines properly so you can
minimize downtimes due to mysql.
Mysql has proven better over the last years in issues like scaling and
stuff.

The biggest problem would be that even if we had DBAL, we would use like 2%
of the other databases potential. So I think we can skip that too. Even more
because you can switch to a different database system with an extension.
I wanted to have DBAL for a long time now but only because mysql keeps
annoying me on a windows server. Suddenly connections aren't reused and
stuff like this. 3 days later the problem is gone. I hate to have a CRON (or
better Task Planner) job running that terminates all running mysql threads
once an hour :)

Plus I think DBAL is more than 3 months of work for two or three guys who
really know what they are doing. The core might be done fast, but very soon
you will have to get to the extensions and there you are... loads of
problems.

My idea:
Let's do DBAL as soon as all developers are bored and don't have anything
else to do ;-)
  or
Let's do DBAL as soon as anyone shows up with a lot of money to sponsor the
whole thing.
Don't forget that while DBAL is running, no core changes may be done,
otherwise we would have to merge stuff which would result in chaos.






More information about the TYPO3-dev mailing list