The session factory does NOT act as first-level cache, that is the responsibility of the session. The main concern for data management is any use of the second-level cache if the same cache key is used for entities from different databases.
On Wednesday, 24 October 2012 10:27:19 UTC+2, Alexander Kot wrote: > Hello > > We are using not 1 SF for each tenant but 1 SF per tenant based on common > Configuration. > For us there 1 blocking feature to use shared SF - HiLo Id generator (both > standard and extended) > HiLo generator for entity is global per SF not per session, so in case of > MultiTenancy with shared SF it will be reused between tenants. > Solution is do not use HiLo or share it's table somehow (1 schema per > tenant + 1 schema with common data HILo, (in our case also logging table > for log4net with tenant_id) ) > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/CsOtjHW60CkJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
