On Sep 23, 2007, at 11:56 PM, Erik Jones wrote:
On Sep 21, 2007, at 6:16 PM, Stefan Arentz wrote:
Well I'm just toying with an idea. The problem I'm facing is that I
would like clients to only see the tuples that they have created and
own. I guess I'll just skip direct sql access to the db a
On Sep 21, 2007, at 6:16 PM, Stefan Arentz wrote:
Well I'm just toying with an idea. The problem I'm facing is that I
would like clients to only see the tuples that they have created and
own. I guess I'll just skip direct sql access to the db and write some
API on top of it that manages the dat
--- Stefan Arentz <[EMAIL PROTECTED]> wrote:
> Well I'm just toying with an idea. The problem I'm facing is that I
> would like clients to only see the tuples that they have created and
> own. I guess I'll just skip direct sql access to the db and write some
> API on top of it that manages the da
> [mailto:[EMAIL PROTECTED] On Behalf Of Stefan Arentz
> Sent: Friday, September 21, 2007 5:39 PM
> To: pgsql-sql@postgresql.org
> Subject: [SQL] Many databases
>
> I'm in a strange situation where it makes more sense to give each user
> it's own database instead of having
I'm in a strange situation where it makes more sense to give each user
it's own database instead of having a single database with users and
permissions. How does PG deal with that? Is it a problem to have have
say a thousand small databases?
S.
---(end of broadcast)--
