[Typo3-dev] DBAL: Call for sponsors

Ingo mailinglisten at i-schmitt.de
Thu Mar 4 10:29:06 CET 2004


Hey All ...
> Hey folks,
> 
> 
> The DBAL will not only be neccessary for using other databases. Much of
> the work for creating the abstraction class(es) will also be necessary
> to make XML queries possible, which will be a very important issue while
> you're using templavoila for instance. Another point is cleaning of
> TYPO3's internal architecture related to database queries.
> 
> After knowing the details of how it will be implemented and what
> positive side effects it will have, I also plead for getting started
> with it right now. If you have a client or are in the position to raise
> some funding, just do it!
> 

I totally agree, that DBAL is one of the top issues for typo3 and we all 
want to have it yesterday. But I think such core changes should be made 
in a separate version (e.g. 3.7.0).

Why ?
I think 3.6.0 is almost ready for production and the last pieces that 
have to be done must be done anyway before starting implementing DBAL at 
all. So you could have 3.6.0 at one point and than going on with 3.7.0.
Testing DBAL Applications takes quite a lot of time, you have to test 
your SLQ-Code with a lot of databases and systems (We have done this in 
other projects ..). This would be a quite long time, for waiting for an 
final Version and currently many people don’t want to change their 
installation to a RC.
With starting DBAL in the core, all new or updated Extensions should use 
DBAL, no more direct mysql calls should be made (The coding guidelines 
should be changed in that point to !). For that reason it would be 
easier to say: My Extension uses DBAL, so you have to have 3.7 (And 
besides the Extension should not be installable in 3.6 and 3.5; 
Currently you have extensions based on 3.6 RC1  you could install on 3.5 
and crash your complete System).  If you put DBAL in 3.6 and emphasis on 
DBAL all new Extension based on 3.6 RC have to be rewritten.

Besides, we will help to develop DBAL the best we can.

Ingo




More information about the TYPO3-dev mailing list