Re: [pgsql-advocacy] What can we learn from MySQL? - Mailing list pgsql-www

From Josh Berkus
Subject Re: [pgsql-advocacy] What can we learn from MySQL?
Date
Msg-id 200404231213.16003.josh@agliodbs.com
Whole thread Raw
In response to Re: [pgsql-advocacy] What can we learn from MySQL?  (Robert Treat <xzilla@users.sourceforge.net>)
Responses Re: [pgsql-advocacy] What can we learn from MySQL?  (Alexey Borzov <borz_off@cs.msu.su>)
List pgsql-www
Folks,

> > * Recommended replication solution (erserver?)
> > * Recommended full-text search solution (tsearch?)
> > * Recommended GUI / web frontend (PGAdmin / phpPgAdmin)
> > * Drivers: ODBC, JDBC, whatever
> > * PostGIS
> > * Banners to put on the website
> > * A description of what to find in the contrib dir

I'm really nervous about pointing to "recommended" solutions where we have
several.   I'd rather have links to all mature projects in that category.

Replication is actually several different problems demanding several different
solutions.   So no one replication solution is going to cover all needs,
ever.

For GUIs, we have an embarassment of them, and I would not want to be
responsible for telling anyone their project is "not recommended".  That's an
effective way of making a lot of enemies in the OSS community.   Instead, I
might suggest listing all OSS GUIs in order of popularity -- which still lets
PGAdmin & phpPGAdmin float to the top, but without telling Xpg or PGAccess to
take a flying leap into the void.

--
Josh Berkus
Aglio Database Solutions
San Francisco

pgsql-www by date:

Previous
From: Robert Treat
Date:
Subject: Re: [pgsql-advocacy] What can we learn from MySQL?
Next
From: Alexey Borzov
Date:
Subject: Re: [pgsql-advocacy] What can we learn from MySQL?