Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] pgaccess - where to store the own data

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Iavor Raytchev <iavor(dot)raytchev(at)verysmall(dot)org>,pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>,pgsql-interfaces <pgsql-interfaces(at)postgresql(dot)org>
Subject: Re: [HACKERS] pgaccess - where to store the own data
Date: 2002-08-31 12:38:03
Message-ID: 20020831203739.G75164-100000@houston.familyhealth.com.au (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-interfaces
> > 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.

These days you could create a schema in the database you're managing as
well...

Chris



In response to

pgsql-hackers by date

Next:From: Gavin SherryDate: 2002-08-31 16:28:21
Subject: Re: [HACKERS] Proposed GUC Variable
Previous:From: Zhicong Leo LiangDate: 2002-08-31 12:28:53
Subject: serial type as foreign key referential integrity violation

pgsql-interfaces by date

Next:From: Iavor RaytchevDate: 2002-08-31 17:55:49
Subject: pgaccess 0.98.8 beta 1 - the show starts
Previous:From: Dave PageDate: 2002-08-30 20:02:51
Subject: Re: [HACKERS] pgaccess - where to store the own data

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group