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

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

From: "Matthew T(dot) OConnor" <matthew(at)zeut(dot)net>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>,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-30 18:43:38
Message-ID: 200208301443.38126.matthew@zeut.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-interfaces
> As someone else mentioned (I think), even using a separate schema is not
> always an acceptable option. If you are using a "packaged" application
> (whether commercial or open source), you usually don't want *any*
> changes to the vendor provided database. Particularly with commercial
> software, that can mean loss of, or problems with, technical support, or
> problems when upgrading.

Agreed, but if the information is to be stored using the database server at 
all, then I think this option should be left in since some users probably 
don't mind the clutter, and will not be allowed to create a new database or 
schemea.

In response to

Responses

pgsql-hackers by date

Next:From: Joe ConwayDate: 2002-08-30 18:51:43
Subject: Re: SRF memory mgmt patch (was [HACKERS] Concern about
Previous:From: Joe ConwayDate: 2002-08-30 18:12:28
Subject: Re: [HACKERS] pgaccess - where to store the own data

pgsql-interfaces by date

Next:From: terryDate: 2002-08-30 19:12:32
Subject: Re: pgaccess - where to store the own data
Previous:From: Joe ConwayDate: 2002-08-30 18:12:28
Subject: Re: [HACKERS] pgaccess - where to store the own data

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