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" ?
