On May 7, 2009, at 10:05 PM, Scott Marlowe wrote:
> On Thu, May 7, 2009 at 1:45 PM, Anders Steinlein
> <anders@steinlein.no> wrote:
>> Hi,
>>
>> I'm pondering a design question for a subscription-based web-app we
>> are
>> developing. Would it be feasible to create a new schema per user
>> account,
>> setting the search_path to their own schema during login?
>>
>> [snip]
>
> We're looking at something similar here at work, but in the 10k to 10M
> range of schemas. I'll let you know how our testing goes.
>
> 1,000 is nothing in terms of schemas. You should be fine.
I'd be *very* interested to hear your experiences once you get some
results.
Generally though, what made you consider such a solution? Same
advantages as I mentioned? One thing I'm a bit usure of how best to
solve is where to place the "users" or some such table for
authentication and other "shared" info -- simply in the "public"
schema, perhaps?
\a.
