From: Matthew T. OConnor <matthew@zeut.net>
To: Joe Conway <mail@joeconway.com>
Cc: Dave Page <dpage@vale-housing.co.uk>
Cc: Iavor Raytchev <iavor.raytchev@verysmall.org>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: pgsql-interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: [HACKERS] pgaccess - where to store the own data
Date: Fri, 30 Aug 2002 14:43:38 -0400
Message-ID: <200208301443.38126.matthew@zeut.net> (raw)
In-Reply-To: <3D6FB58C.4010501@joeconway.com>
References: <03AF4E498C591348A42FC93DEA9661B8677C@mail.vale-housing.co.uk>
<1030730363.13569.5.camel@zeutnull>
<3D6FB58C.4010501@joeconway.com>
> As someone else mentioned (I think), even using a separate schema is not
> always an acceptable option. If you are using a "packaged" application
> (whether commercial or open source), you usually don't want *any*
> changes to the vendor provided database. Particularly with commercial
> software, that can mean loss of, or problems with, technical support, or
> problems when upgrading.
Agreed, but if the information is to be stored using the database server at
all, then I think this option should be left in since some users probably
don't mind the clutter, and will not be allowed to create a new database or
schemea.
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-interfaces@postgresql.org
Cc: matthew@zeut.net, mail@joeconway.com, dpage@vale-housing.co.uk, iavor.raytchev@verysmall.org, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] pgaccess - where to store the own data
In-Reply-To: <200208301443.38126.matthew@zeut.net>
* 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