[TYPO3-dev] DBAL - does it actually work

[ries van Twisk]

On Nov 11, 2008, at 3:19 AM, Michael Greiner wrote:

> Hello,
>
> my experiences with dbal and postgres so far are bad. For any reason  
> since I
> switched to 4.2.2 the Extension Manager doesn't work anymore. This  
> is just
> the very latest example for random behaviour. Prepare for a lot of
> rewriting.
> Most extensions don't work cause people write strictly for mysql. So  
> noone
> cares about coding guidelines. I did both: migrating and a new setup  
> and
> both
> is a mess. Typo3's origin is with Mysql. Unless you are willing wo
> rewrite many
> many lines of code and talk to many different developers about  
> things you've
> never heard of before, stay away from running it on Postgres.

If you want something easy then stay away from any DB other then MySQL.
However it's not as bad as it sounds like, it's doable to run TYPO3 on  
PostgreSQL
and on I believe it was possible to run TYPO3 on oracle aswell (core  
people
made even changed to core for that).

The problem with DBAL is that the API is far from complete to be  
called DBAL,
in its current stage it doesn't try to abstract anything rather then  
mangle with SQL and to
re-route requests to a other system other them MySQL

I have been writing a myself a sqlite driver and a PostgreSQL driver  
for TYPO3
and core was more then happy to run on it. (With teh SQLite driver you  
could
directly see how often TYPO3 core wasn't closing any resources which  
was kinda fun to watch...)

However EM wouldn't work aswell as the extension manager, both tools
are bypassing the API (TYPO3_DB) completely because TYPO3_DB simply
doesn't have enough functions to support both systems.


Apart from that it's duable, but expect some work.

Ries



>
>
> Michael