> Separate DBs sounds messy. Some elaboration on that point.
Methinks you will lose the advantage of connection pooling. Every request will need its own connection, and performance will suffer. How will you avoid duplicate db names? You will need a central repository, which probably should be another db. This set of connections could pool, though. At some point your rdbms will impose a penalty for keeping track of so many db's, assuming you get a lot of users. The Web2py manual elaborates on multi-tenancy at http://web2py.com/books/default/chapter/29/6#Common-fields-and-multi-tenancy<http://web2py.com/books/default/chapter/29/6#Common-fields-and-multi-tenancyhere> On Friday, July 20, 2012 1:15:08 AM UTC-4, Alec Taylor wrote: > > On Fri, Jul 20, 2012 at 4:12 AM, Andrew <awillima...@gmail.com> wrote: > > If users can create groups, will you want to create a database on the > fly? > > > > Yes. In the same way that in Massimo talk from a few months ago he > talked about using the multi-tenant feature in an e-commerce setup, > presumable where individuals would click a button "Create a new > shop"... > > My use-case is quite similar. > > On Fri, Jul 20, 2012 at 8:22 AM, pbreit <pbreitenb...@gmail.com> wrote: > > Separate DBs sounds messy. You could either use Web2py's multi-tenant > > functionality and/or auth_group. Or just code it. > > > > Could you please elaborate? > --
