On Wed, 7 Jan 2004, Martijn van Oosterhout wrote:
> Are you actually going to be doing joins between these applications?
> If not, why not setup multiple databases, then you can be sure they
> won't conflict.
Well in at least one situation I can think of there will be joins. And
with a minimum o
On Jan 6, 2004, at 3:27 PM, Oliver Elphick wrote:
On Tue, 2004-01-06 at 22:06, Adam Ruth wrote:
1. Modifying the applications to use schemas instead of connecting to
specific databases. Getting the authors to use schemas so I do it
once.
One thing I'd suggest would be to modify the applicat
On Tue, Jan 06, 2004 at 03:34:21PM -0800, Roderick A. Anderson wrote:
> On Tue, 6 Jan 2004, Oliver Elphick wrote:
>
> > You can use ALTER DATABASE to set that up permanently, without touching
> > the application.
>
> I'd thought of this but since there will be several applications installed
> an
On Tue, 6 Jan 2004, Oliver Elphick wrote:
> You can use ALTER DATABASE to set that up permanently, without touching
> the application.
I'd thought of this but since there will be several applications installed
and some, I am sure, will have same-named tables this could back-fire.
Rod
--
"
On Tue, 6 Jan 2004, Adam Ruth wrote:
> One thing I'd suggest would be to modify the application to issue a
> "set search_path = yourschema;" at the beginning, then the rest of the
> application wouldn't need to change. That's what I did when I did
> something similar.
Neat idea. I was thinki
On Tue, 2004-01-06 at 22:06, Adam Ruth wrote:
> > 1. Modifying the applications to use schemas instead of connecting to
> >specific databases. Getting the authors to use schemas so I do it
> >once.
>
> One thing I'd suggest would be to modify the application to issue a
> "set search_path
1. Modifying the applications to use schemas instead of connecting to
specific databases. Getting the authors to use schemas so I do it
once.
One thing I'd suggest would be to modify the application to issue a
"set search_path = yourschema;" at the beginning, then the rest of the
applicati