-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Multi-Tenant] tenantSettings
table in backend
#3127
Comments
2 tasks
@njlie the unique id - could we instead use a composite key (tenantId, TenantSetting) as the primary key (without needing another id)? |
Late response, but that's the idea, this composite key would indeed be the primary key. |
6 tasks
6 tasks
tenantSettings
table in backendtenantSettings
table in backend
6 tasks
6 tasks
6 tasks
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the introduction of mulit-tenancy, some environment variables will have to be come tenanted. To represent the tenancy of these variables, the
tenantSettings
table will hold them. The unique id of rows on this table will not be generated, but will instead be a concatenation of thetenantId
it is for and the name of the value it represents. For example:The tenant settings table schema should look like this:
tenantSettings
tablemodel.ts
file fortenantSettings
tablePrerequisites
backend
tenants table #3103The text was updated successfully, but these errors were encountered: