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

[Stefan Kreisberg, LinkFactory]

One could also argument that the current database abstraction layer is 
just, as I understand the many comments, going to be as close to std. SQL 
as possible. Like with the sub-queries, AFAIK the MySQL Team has 
implemented those in 4.x or plan to in 5.somnething - a further 
advancement for following the "in my eyes" fairly strict and homogenous 
SQL api SQL-92 (or is it 99 now?)

So, IMHO I find such an encapsulationlayer suitable for 
high-end-production schemes where huge non-standard enterprise systems 
needs to talk to one another, but not for webbrowsing content management 
experiences ;-)

5 cents and over...

Cheers,

-Strato, Typo3WannaBee

On Mon, 16 Feb 2004 15:10:53 +0100, Kasper Skårhøj <kasper at typo3.com> 
wrote:

>
>> much, aside from a nice buzzword to print on the box (if you print
>> one).
>
> Unfortunately this is sometimes powerful.
>
>
> I'm not opposed to DBAL but I'm just realistic about implications.
> If I want to have DBAL its for the sake of others, not myself.
> I don't care much for object persistence. Not my style of coding, seems 
> to add lots of overhead. I'm more down-to-earth for that. I never liked 
> it.
> And using MySQL exotic features; The most advanced SQL I have had to 
> write was joins and usage of AVG, SUM and COUNT in queries - and 
> subselects which we unfortunately don't have. But the point: Even if 
> MySQL would forever be the TYPO3 database, I'm not in support of MySQL 
> specific SQL on a deeper level if it can be solved in a more general 
> way; because why make it harder to do DBAL in the future it one should 
> decide to?
> - kasper
>
> --------------------- o ---------------------
> "Mange kokke fordærver maden."
> "En fugl i hånden er bedre end ti på taget."
>
>