Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 1EF8A475CA9; Fri, 30 Aug 2002 11:53:20 -0400 (EDT) Received: from joeconway.com (unknown [63.210.180.150]) by postgresql.org (Postfix) with ESMTP id 54B14475C77; Fri, 30 Aug 2002 11:53:19 -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 1317086; Fri, 30 Aug 2002 08:38:44 -0700 Message-ID: <3D6F9490.9040507@joeconway.com> Date: Fri, 30 Aug 2002 08:51:44 -0700 From: Joe Conway 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: Iavor Raytchev Cc: pgsql-hackers , pgsql-interfaces Subject: Re: pgaccess - where to store the own data References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200208/90 X-Sequence-Number: 3052 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