Date: Wed, 21 Apr 2004 13:28:03 -0400
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-general@postgresql.org
Subject: Re: Replication
Message-ID: <20040421172803.GA325@phlogiston.dyndns.org>
Mail-Followup-To: pgsql-general@postgresql.org
References: <CAC2F23E-92AC-11D8-B5ED-000A95DE2550@ifrance.com>
	<20040420115108.GC29715@phlogiston.dyndns.org>
	<40869207.8020509@Yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40869207.8020509@Yahoo.com>
User-Agent: Mutt/1.5.5.1+cvs20040105i

On Wed, Apr 21, 2004 at 11:23:51AM -0400, Jan Wieck wrote:
> for that is NOT performance. SAP spends that effort multiple times by 
> implementing their own, custom integrity control and data domain system 
> in the DB abstraction layer, to gain DB vendor independence. That 
> abstraction layer is larger than PHP and Apache together, so this 
> example is IMHO totally irrelevant for the typical MySQL user.

Actually, I think it _is_ relevant.  It's proof, IMNSHO, that the
strategy of "doing it in the client" is completely bankrupt.  It's
one thing to do it this way if you have software which is a
category-killer the way SAP is, because you can afford the overhead
of all those developers doing all that extra work, and you can make
your customers buy trillion-dollar hardware to run your bloated
masterpiece.  The Rest Of Us, however, need to do things efficiently,
and that means doing the work in the place where it is least likely
to need to be checked again.  For most database applications, that's
inside the database.  (I'll not now start my rant on the mess caused
by developers who are careless with this principle.)

A

-- 
Andrew Sullivan  | ajs@crankycanuck.ca
The plural of anecdote is not data.
		--Roger Brinner