re: the multitude of config choices, I think this is dangerous and likely to
cause troubles.

As NH is presently designed, writing "new Configuration()" results in NH
reading config info from whatever source is 'discoverable' by it (e.g., NH
section in app.config OR hibernate.cfg.xml).  Indiscriminately adding
entries into one or more of these places when the user isn't already using
that place to store their config info is troubling to me (violates the
principle of least surprise).

However, what I could get behind is the following:

   - add a sample hibernate.cfg.xml file in the 'packages/<package-name>'
   folder that the user could then review and *manually* copy-paste content out
   of into whatever config system of choice they want to use

IMO this would more safely solve what you're trying to achieve: providing
'sample' config for the package added so that the user needn't google for
blogs telling them how to configure (example) the second-level cache
provider they just chose.


Steve Bohlen
[email protected]
http://blog.unhandled-exceptions.com
http://twitter.com/sbohlen


On Mon, Mar 14, 2011 at 12:48 PM, Patrick Earl <[email protected]> wrote:

> It would come with a dependency on Npgsql and the typical properties
> used to set up a PostgreSQL connection.
>
> Regarding the proliferation of configuration systems, I think it would
> be reasonable to select a minimalistic mechanism for NuGet packages to
> specify properties.  If people are already using different
> configuration systems, then I don't imagine adding to an unused config
> section would make any difference.  If they're not, then they would
> undoubtedly like the boost that the example configuration provides.
>
> I think that most of the differentiation in the area of configuration
> is around how to specify mappings.  For a basic scenario, it's not
> necessary to have complicated ways of specifying the proxy provider or
> database connection information.  Could not this standard information
> be placed in the config file, even if it only ends up being used as an
> example by the end user?
>
> Hunting down the different config strings for proxies, databases, and
> such is more work than finding the dlls.
>
>        Patrick Earl
>
> On Mon, Mar 14, 2011 at 10:23 AM, Fabio Maulo <[email protected]>
> wrote:
> > What mean "NHibernate.Databases.PostgreSQL" ?
>

Reply via email to