Feature Request for an Updatable SessionFactory

[Ganesh13024]

Hello NHiberbate Team,

This request pertains to a feature enhancement related to the current implementation of NHibernate and its SessionFactory. I have already outlined our requirements in the NHUsers thread and would like to extend my gratitude to Mr.Frédéric Delaporte for providing a detailed explanation regarding the immutability of the SessionFactory and its internal components.

Our use case involves a dynamic table schema that is not fixed or standardized. The schema is subject to changes at runtime, and consequently, the mappers are also updated to reflect these changes. While attempting to propagate these mapper updates to the SessionFactory, I encountered a significant limitation: the SessionFactory requires a complete rebuild to accommodate these changes. Unfortunately, this rebuilding process is time-intensive due to the heavy computational cost associated with metadata extraction.

Given the critical role of the SessionFactory in managing database interactions, the inability to update it dynamically poses a challenge in scenarios where frequent schema changes occur. This has led me to consider the feasibility of an updatable SessionFactory that could adapt to runtime changes without necessitating a full rebuild. Such a feature would drastically improve performance and streamline our workflow, particularly in environments where schema evolution is a regular occurrence.

I am aware that ensuring concurrency control in such a system is complex and that threading mechanisms would be essential to achieving this. However, an updatable SessionFactory could mitigate the performance bottlenecks associated with rebuilding and offer a more efficient solution for runtime adaptability.

I hope this provides a clearer understanding of the issue and the motivation behind the feature request. I welcome any further insights or recommendations on how to approach this challenge effectively.

Additionally, I am attaching my SessionFactory build-time changes based on the number of mappers. Could you please consider this scenario as well in the ORM implementation?

Best regards,
Ganeshkumar M