Do you have any particular ideas on why it may not work?
I must admit I am not well aware of internals of cache frameworks but AFAIK Hazelcast uses keys and hashcode as data store keys which might be same for objects persisted in different databases. How can we segregate/partition data for different DBs in Hazelcast?
Seems like a valid concern, but needs deeper investigation.
Perhaps you should either avoid using Hazelcast and entity/query caches at all, or use only entity cache for entities with UUID keys.
1 Like
Hi Jmix Team!
Jmix version: 2.4.4
Jmix Studio plugin version: 2.5.1-243
We have been working on a multi-tenancy project for a year. Now we want to make it a multi-database project with one database for each tenant. But if we export the user table with tenants to the shared database as shown in the example, there are too many entities in the main database linked to user and tenant tables. Then of course it gives errors like ERROR: relation "public.jb_user" does not exist. What advice can you give for such kind of cases?
So how can we join the user table to the entities in the main db?
A trivial idea: create the User table and entity in the main DB and insert records with users of the corresponding tenant.