> -----Original Message----- > From: Joe Conway [mailto:[EMAIL PROTECTED]] > Sent: 30 August 2002 16:52 > To: Iavor Raytchev > Cc: pgsql-hackers; pgsql-interfaces > Subject: Re: [HACKERS] [INTERFACES] pgaccess - where to store > the own data > > > 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. I thought of using that approach with pgAdmin, but how do you ensure that new users use the correct database as the repository, or, if you hard coded it to use a 'pgaccess' database (for example), how do you deal with security etc on a shared system such as might be run by an isp? Of course, in 7.3 you could just create a pgaccess schema in each database... Regards, Dave. ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
