isis-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeroen van der Wal <>
Subject Re: Mult-Tenancy
Date Wed, 18 May 2016 20:50:32 GMT
Hi Sunand,

Because we needed more sophistication we've gone for option 3 and not
implemented 1 and 2 but Datanucleus should be able to support those
scenarios  [1]. What use case are your trying to solve?




On 18 May 2016 at 19:08, sunand p <> wrote:

> Hi,
> We have Isis-Security module as an addon which provides multi-tenancy
> feature. Presently multi-tenancy as I understand is with respect to
> associating an user to a tenant and assigning roles and permissions. "*Each
> user can be associated with a particular tenancy, and Isis can then be
> configured such that they cannot access data in other tenancies*"
> As for data, multi-tenancy is achieved via following ways,
> 1) Have a separate schema per tenant and have the tables created within the
> schema and refer to it as (for example) *tenant1_schema.table1*
> 2) Have a separate database assigned to a tenant and keep all the data in
> that DB.
> 3) Store all data in one table and have a tenant id discriminator. Include
> the discriminator in the query framework after resolving a tenant add the
> where clause to each query (For example) Select * from Table1 where
> tenantId = 'tenant1'
> As for Apache Isis how can I support Option 1 and Option 2 in the current
> framework?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message