Tom,
> > I've got one in the works for http://databasejournal.com/, and I
was
> > hoping someone could look it over for me to catch any egregious
errors.
I'm on vacation, so I don't have the ability to test the actual SQL.
The
article text is fine. You might want to, in future articles, suggest
that
people run EXPLAIN ANALYZE and not just EXPLAIN in order to see when
the
query planner is estimating wrong.
BTW, the queries that GForge uses to generate the category counts for
the
trove map are egregiously bad and generate wrong counts to boot.
They're
basically a loop of queries, one *per category*, when the whole thing
could
be done in a single query. I've been meaning to fix this for some
time,
but I got hung up on getting GForge installed on my dev machine. Maybe
later ...
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
