On Wednesday, June 17, 2015 at 4:42:57 PM UTC-4, 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? >
No difference between Auth tables and any other tables made up of the same types of fields/numbers of records, etc. Do you really expect millions of *concurrent* users -- that sounds like Facebook/Google scale? Anyway, I assume you're a good ways off from that scale, so probably not worth worrying about too much at this point. Anthony -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
