Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-5249

Implicit multi-tenancy by naming convention

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      Many data models have a naming convention for the tenantId. It would be useful to define that convention with an optional Phoenix property in config, so if a tenant-specific connection is opened and a table is queried that has that tenantId column name in its PK, multi-tenant behavior automatically occurs even if MULTI_TENANT is not set in the table's metadata. (If MULTI_TENANT is explicitly false, multi-tenant behavior would not occur.)

      Attachments

        Issue Links

          depends upon

          Improvement - An improvement or enhancement to an existing feature or task. PHOENIX-5248 Allow MULTI_TENANT to use any PK column

          • Major - Major loss of function.
          • Open
          is depended upon by

          New Feature - A new feature of the product, which has yet to be developed. PHOENIX-3939 Tenant-based Replication

          • Major - Major loss of function.
          • Open

          Activity

            People

              gjacoby Geoffrey Jacoby
              gjacoby Geoffrey Jacoby
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: