Derive from DriverConnectionProvider or implement IConnectionProvider. Load the facilityid (or whatever) and the associated connection strings once, and then hand them out using the custom provider. You will only need one session factory that way.
- Robert On Mon, Apr 26, 2010 at 1:02 PM, Sam <[email protected]> wrote: > (this is a cross-post) > We're using StructureMap to manage NH's sessionFactories and have come > across a > problem that we can't elegantly figure out. (currently we're hacking > away at it). > We have a 3 main legacy databases that we talk to, but there's a > chunk > of data that's very specific for each facility (hospital's physical > location) that we must get at runtime and is based on the facility > Id. This connection string is stored in a resource table in another > database. > I'm unsure which approach would be best: > > 1.) Create a dictionary at app startup that stores away the hundreds > of connection strings. This dictionary is then used to create the > sessionFactories (as singletons) just in time? > 2.) Create SM profiles? > 3.) another approach? > > We require that our sessions live through the http request only. > > - Sam > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<nhusers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "nhusers" group. 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.
