[development] Do not let postgresql hold back great patches

[Larry Garfield]

On Sunday 02 December 2007, Khalid Baheyeldin wrote:
> On Nov 30, 2007 9:47 AM, Bill Moran <wmoran at potentialtech.com> wrote:
> > I expect that the right way to make Drupal _truly_ database neutral is
> > to have database-dependent and database-independent code.  You'd only
> > see this kind of thing at the lower levels, and higher logic code
> > shouldn't even care about it.
>
> The alternatives are:
>
> 1. Calling modules would do 'case' statements for each type of database. No
> one wants that, unless it is a highly optimized site with lots of
> customization ( i.e. not the normal Drupal core).
>
> 2. Use the lowest common denominator for SQL and live with performance and
> scalability issues.
>
> 3. Do database specific stuff (including optimization) in the abstraction
> layer (this is what Bill Moran advocates above).
>
> I am for #3 as the way forward.

#3 is what I'm pushing for in the D7 database overhaul, within reason.  How to 
abstract everything without making the syntax insane or the performance 
terrible is what I'm currently trying to wrap my head around.  The biggest 
problem is field type handling, which I want to keep away from module 
developers but varies greatly depending on the database.

-- 
Larry Garfield			AIM: LOLG42
larry at garfieldtech.com		ICQ: 6817012

"If nature has made any one thing less susceptible than all others of 
exclusive property, it is the action of the thinking power called an idea, 
which an individual may exclusively possess as long as he keeps it to 
himself; but the moment it is divulged, it forces itself into the possession 
of every one, and the receiver cannot dispossess himself of it."  -- Thomas 
Jefferson