From: Joe Conway <mail@joeconway.com>
To: Iavor Raytchev <iavor.raytchev@verysmall.org>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: pgsql-interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: pgaccess - where to store the own data
Date: Fri, 30 Aug 2002 08:51:44 -0700
Message-ID: <3D6F9490.9040507@joeconway.com> (raw)
References: <HKEIIDPFPDBMOMDLIEEGGENOCNAA.iavor.raytchev@verysmall.org>
Iavor Raytchev wrote:
> Hello everybody,
>
> There is an open question we need broad opinion on.
>
> Currently pgaccess stores its own data in the database it works with.
> Some people do not like that. To store it elsewhere invokes a number of
> issues such as:
>
> - where is this somewhere
> - converting form all versions to the new
> - etc.
>
> What do people think about this. Is it so bad that the own data is
> stored in the database pgaccess works with?
>
I don't particularly like it. Oracle deals with this by having a
database unto itself as a management repository (Oracle Enterprise
Manager, OEM, I believe). You register the database you want to manage
with the repository, and the metadata is kept there instead of in each
managed database.
Joe
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: mail@joeconway.com, iavor.raytchev@verysmall.org, pgsql-hackers@postgresql.org
Subject: Re: pgaccess - where to store the own data
In-Reply-To: <3D6F9490.9040507@joeconway.com>
* 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