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
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,
Didn't mean to use *permissions* ambiguously.
db.auth_group will contain the role e.g., SME, and db.auth_membership
will contain the IDs of people in that SME role.
but what does this mean: *million users doesn't really qualify for a single
postgres database*? That a million users is too
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
4 matches
Mail list logo
