Ahh, yeah, protected internal is a much better choice and works like a champ.
I've also sent a patch to your email for the basic Oracle configuration. It's not real "feature rich," but contains the formatted connection string and a few options that we commonly set (for connecting to PeopleSoft and a vendor-specific app) and tests. Compiled and added into a project I'm working on right now all seems well. ;) -dl ------------------------------ *David R. Longnecker* Blog <http://blog.tiredstudent.com> | Twitter<http://www.twitter.com/dlongnecker>| Linked In <http://www.linkedin.com/in/davidlongnecker> On Wed, Feb 25, 2009 at 4:53 PM, James Gregory <jagregory....@gmail.com>wrote: > I'm only dashing here, so I can't give a proper answer. What you're doing > sounds right, the IsDirty really should be protected internal rather than > just internal; it's internal so it doesn't show up for consumers of the > interface, but that obviously stops inheritors from using it too! > On a side note, I'd actually be very interested in receiving a patch for an > Oracle configuration. We've had it requested before but I don't have the > experience nor software to be able to write it. > > On Wed, Feb 25, 2009 at 8:43 PM, David R. Longnecker < > tiredstud...@gmail.com> wrote: > >> Good day! >> >> I've been investigating the latest Fluent NH drop (b 366) and stumbled >> onto an issue. Previously, I had built up a custom OracleConfiguration to >> handle connecting to our various Oracle databases. Using the other >> configurations as a model, I inherited from PersistenceConfiguration and all >> was well. >> >> Under the latest build, simply setting the configuration wasn't enough (or >> whatever 'wrong' way I was using was fixed (^_~)). >> >> I received the following error: >> >> *NHibernate.HibernateException *: Could not find connection string setting >> (set connection.connection_string or >> >> connection.connection_string_name property) >> >> After stepping through, I found that I needed to set the IsDirty flag on >> the properties for PersistenceConfiguration.CreateProperties() to generate >> the appropriate key--leaving it as 'false' simply skipped over it. >> >> Unfortunately, the IsDirty flag is set to internal. I've downloaded the >> source and set it to public to test, then added the IsDirty flags to each of >> my OracleConnectionStringBuilder fluent methods--and it works like a champ. >> >> Is there a perscribed method to build custom database configurations for >> Fluent NHibernate? >> >> - As I've done in the past, simply create a class and inherit from >> PersistenceConfiguration<T, K> and set IsDirty to public instead of >> internal? >> - Submit validated configurations as a patch for the project so they >> can take advantage of internal flags? >> - Rather than inherit and creating a custom configuration, should I >> skip the ConnectionStringBuilder and call Raw/ConnectionString.Is >> directly? >> - Another? >> >> Thanks everyone! >> >> -dl >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
