Re: [HACKERS] pgaccess - where to store the own data - Mailing list pgsql-interfaces

From Dave Page
Subject Re: [HACKERS] pgaccess - where to store the own data
Date
Msg-id 03AF4E498C591348A42FC93DEA9661B8677C@mail.vale-housing.co.uk
Whole thread Raw
Responses Re: [HACKERS] pgaccess - where to store the own data  ("Matthew T. OConnor" <matthew@zeut.net>)
List pgsql-interfaces

> -----Original Message-----
> From: Iavor Raytchev [mailto:iavor.raytchev@verysmall.org]
> Sent: 30 August 2002 16:44
> To: pgsql-hackers; pgsql-interfaces
> Subject: [HACKERS] pgaccess - where to store the own data
>
>
> 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 had the same trouble with pgAdmin, especially with pgAdmin I which had
a whole host of objects server-side. I also found that people didn't
like it, but where else do you store the data?

pgAdmin II no longer uses such tables, but to get over the problem as
best I could, I added a cleanup option to pgAdmin I that removed all
server side objects in one go.

Regards, Dave.


pgsql-interfaces by date:

Previous
From: Lee Kindness
Date:
Subject: [HACKERS] 7.3 gotchas for applications and client libraries
Next
From: "Dave Page"
Date:
Subject: Re: [HACKERS] pgaccess - where to store the own data