BTW: a million users doesn't really qualify for a single postgres database, no matter what.
On Wednesday, June 17, 2015 at 11:17:39 PM UTC+2, Niphlod wrote: > > auth_group is for groups. auth_permissions is for permissions. as any > other table in your db, the problem is not the # of records, rather than > what query you need to do on those. > > On Wednesday, June 17, 2015 at 10:42:57 PM UTC+2, Alex Glaros wrote: >> >> db.auth_group is doing double duty in my app as a role table for >> everything in addition to permissions. Examples: (a) Partnership roles with >> the organization. (b) Employee roles such as SME for a project. There may >> be millions of people reading/writing concurrently. >> >> Is there anything different about auth tables from any other table that >> would slow things down? (will be on Postgres/Pythonanywere.com) >> >> Can it handle as many records as regular table? >> >> thanks, >> >> Alex Glaros >> > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
