From: Theo Kramer <theo@flame.co.za>
To: pgsql-docs@postgresql.org
Subject: Re: FAQ on Embedding Postgres
Date: Thu, 06 Mar 2008 08:54:23 +0200
Message-ID: <1204786463.2332.11.camel@localhost6.localdomain6> (raw)
In-Reply-To: <11585.1204784735@sss.pgh.pa.us>
References: <200803051502.m25F2fm03349@momjian.us>
<718.1204738553@sss.pgh.pa.us>
<20080305174126.GM19860@fetter.org>
<1029.1204739761@sss.pgh.pa.us>
<20080305182500.GN19860@fetter.org>
<20080305103043.233761e8@jd-laptop>
<20080305105307.2bcce254@jd-laptop>
<20080305191717.GV4755@alvh.no-ip.org>
<Pine.GSO.4.64.0803051830040.3352@westnet.com>
<11585.1204784735@sss.pgh.pa.us>
On Thu, 2008-03-06 at 01:25 -0500, Tom Lane wrote:
> Greg Smith <gsmith@gregsmith.com> writes:
> > I think it's funny to consider a specific recommendation for SQLite as
> > being out of line when you look at the history here. The whole reason
> > that software even exists is because of the difficulty of using PostgreSQL
> > in this context. See http://www.linuxjournal.com/article/6650
>
> I've got nothing against SQLite. But I am unhappy with the idea of us
> recommending *any* particular bit of software that is not under our
> control, especially in a document that is as widespread and hard to
> update as our FAQ. There are any number of scenarios where we might
> want to take back such an endorsement, but once made it'll be out there
> somewhere on the Web until cockroaches rule the earth. There is also
> the whole class of arguments about "why'd you recommend X and not Y?"
> that we'd surely get sucked into. Better not to go there in the first
> place.
From a users point of view - both PostgreSQL and other embedable
databases aka file handlers
I have to agree - suggesting an alternate product might belong in a book
but not in a FAQ which is relevant to PostgreSQL and an integral part of
the PostgreSQL documentation.
--
Regards
Theo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: theo@flame.co.za
Subject: Re: FAQ on Embedding Postgres
In-Reply-To: <1204786463.2332.11.camel@localhost6.localdomain6>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox