Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 661CA476A7D for ; Tue, 3 Sep 2002 09:27:49 -0400 (EDT) Received: from relay04.roc.frontiernet.net (relay04.roc.frontiernet.net [66.133.131.37]) by postgresql.org (Postfix) with ESMTP id 8762F47653C for ; Tue, 3 Sep 2002 09:25:19 -0400 (EDT) Received: (qmail 12121 invoked from network); 3 Sep 2002 13:25:22 -0000 Received: from unknown (HELO there) ([170.215.128.148]) (envelope-sender ) by relay04.roc.frontiernet.net (qmail-ldap-1.03) with SMTP for ; 3 Sep 2002 13:25:22 -0000 Content-Type: text/plain; charset="iso-8859-1" From: terry Organization: None To: pgsql-interfaces@postgresql.org Subject: Re: pgaccess - where to store the own data Date: Tue, 3 Sep 2002 09:54:01 -0400 X-Mailer: KMail [version 1.3.2] References: <03AF4E498C591348A42FC93DEA9661B88446@mail.vale-housing.co.uk> In-Reply-To: <03AF4E498C591348A42FC93DEA9661B88446@mail.vale-housing.co.uk> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020903132520.8762F47653C@postgresql.org> X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/22 X-Sequence-Number: 3083 >> how do you deal with security etc on a shared system such as might >> be run by an isp? Hmmm. Does this indicate that pgaccess maybe needs to be forked into a true admin tool and a true end-user/application developer tool? >> Of course, in 7.3 you could just create a pgaccess schema in each >> database... That sounds good, but I'ld still like the ability to access tables from multiple databases too. terry