Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP
	id 191AD475FF1; Fri, 30 Aug 2002 14:14:17 -0400 (EDT)
Received: from joeconway.com (unknown [63.210.180.150])
	by postgresql.org (Postfix) with ESMTP
	id 0DD0A476ADE; Fri, 30 Aug 2002 14:14:08 -0400 (EDT)
Received: from [192.168.5.3] (account jconway HELO joeconway.com)
	by joeconway.com (CommuniGate Pro SMTP 3.5.9)
	with ESMTP-TLS id 1317199; Fri, 30 Aug 2002 10:59:26 -0700
Message-ID: <3D6FB58C.4010501@joeconway.com>
Date: Fri, 30 Aug 2002 11:12:28 -0700
From: Joe Conway <mail@joeconway.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Matthew T. OConnor" <matthew@zeut.net>
Cc: Dave Page <dpage@vale-housing.co.uk>,
	Iavor Raytchev <iavor.raytchev@verysmall.org>,
	pgsql-hackers <pgsql-hackers@postgresql.org>,
	pgsql-interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: [HACKERS] pgaccess - where to store the own data
References: <03AF4E498C591348A42FC93DEA9661B8677C@mail.vale-housing.co.uk>
	<1030730363.13569.5.camel@zeutnull>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200208/91
X-Sequence-Number: 3053

Matthew T. OConnor wrote:
> One thought is to use a completely separate database, but also allow it
> to be stored in the current database if the user wants it too.  This
> also solves the case of a user that can't create a new database for his
> admin tool (permissions etc...).  Also, it might be cleaner now that we
> have schemea support to create one pgadmin, or pgaccess schemea in the
> database, that handled all the others.
> 

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.

Joe