Hello, I'm looking at NH as one plausible upgrade path to address some performance and memory issues we've had with our application as of late as one radical option from what we currently do, which is basically heavy weight domain objects: including both database parts and so on.
We've got an application where to help with performance and indexing and such, data is partitioned across a plethora (and that's light usage of the word) of databases. There are, as far as I can tell, two flavors of databases for most data across the entire application, and a third for use as a sort of librarian. We are using Sql Server 2008 and also are using the master as a template for new models, from which we run a script to upgrade, followed by a series of pluggable Database Updaters for more recent upgrades. In FNH users' experiences, how can something like this be handled in FNH, where SessionFactory and Session are concerned? NH likes to manage one Session per thread? But how about when those sessions can vary from Database flavor to flavor, and across many databases? Best regards, Michael -- You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to fluent-nhibernate@googlegroups.com. To unsubscribe from this group, send email to fluent-nhibernate+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en.
