[development] Do not let postgresql hold back great patches
wmoran at potentialtech.com
Fri Nov 30 18:40:32 UTC 2007
In response to "Edward Z. Yang" <edwardzyang at thewritingpot.com>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> > Take, for example, that COUNT(*) is _really_ fast on MySQL + MyISAM,
> > but is slow on just about every other DB. So, replace it with
> > $db->count(), which does an SQL COUNT(*) on MySQL + MyISAM, but uses
> > some other technique on other databases. The programmer no longer
> > cares _how_ such a thing gets done, he only cares that he wants to
> > know how many rows are in a particular query
> The primary problem with this approach (at least in my experience) is
> that the moment you need to create queries that are even somewhat
> complicated the abstraction layer proves to be insufficient. Ad hoc
> queries are often very useful for performance reasons, but you'll have
> to get a PostgreSQL guru to write an equivalent.
> Then again, for most people writing SQL performance/complex joins/etc
> are not a primary concern...
Well, if such an abstraction solves 90% of the problems, the gurus will
have more time to deal with the remaining 10%.
Assuming it can be done well enough to actually solve 90%.
More information about the development