[TYPO3-core] RFC: MM_foreign_select

[Martin Kutschker]

Karsten Dambekalns <karsten at typo3.org> writes on 
Mon, 13 Mar 2006 16:23:35 +0100 (MET):

> Hi.
> 
> On Sunday 12 March 2006 11:26, Martin Kutschker wrote:
> 
> > I'm still dreaming of a a pure DB connector without the fancy
> > multi-db-handle-and-parse-everything. All I ever wanted was a class
> > that
> > overides t3lib_db with the appripriate low-level-calls to
> > postgresql, ms
> > sel or oracle. DBAL is cool, but seems to be more overhead than
> > necessary if I simply wnat to replace Mysql with another db.
> 
> Right in a way. But why switch then? :)


Heh? Switch to what? There are plenty reasons to switch away from mysql - the customer is always right ;-)

But if I could choose I'd go for a switch without DBAL.


> Anyway, you could just write a customized handler for DBAL that
> shortcuts a lot of the stuff already.


I have to admit I only had some glimpses into the DBAL code yet.


> > No. You need to quoute all identifiers to be forward compatible.
> > Direct
> > mailer broke when Mysql added the "mid" function as it has a column
> > with the name "mid".
> 
> Well, this seems theoretical, in a way. How often does this happen in
> real life?


You'll never know especiall if you're switching the DB. Of course DBAL handles that, right? But it would be needed in the theoretical non-Mysql-without-DBAL setup. You just can't know what names are reserved words in other RDBMS's.

Masi