You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a large database which has clustered indexes on the tenant id, which sadly doesn't form part of the primary key. I have 10 years of legacy code using nhibernate and hundreds of mappings I'd need to update so I am not really keen to update the keys on the nhibernate side if I can avoid it - this led me to think that if I could implement the discriminator multi tenancy strategy, my entity gets would start to make use of that clustered key.
Has anyone given any thought to implementing it, maybe even have a partial implementation in their fork, or able point me in the right direction to get started?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a large database which has clustered indexes on the tenant id, which sadly doesn't form part of the primary key. I have 10 years of legacy code using nhibernate and hundreds of mappings I'd need to update so I am not really keen to update the keys on the nhibernate side if I can avoid it - this led me to think that if I could implement the discriminator multi tenancy strategy, my entity gets would start to make use of that clustered key.
Has anyone given any thought to implementing it, maybe even have a partial implementation in their fork, or able point me in the right direction to get started?
Beta Was this translation helpful? Give feedback.
All reactions