Newbie Question - manually configuring NHibernate.Dialect

damiensawyer · **Posted:** Thu May 19, 2005 1:51 am

Hi all,

Sorry if this question seems blatently obvious... however I can't seem to find an answer.

How do I configure NH manually (ie, without the app.config file)?

Where for example do you set NHibernate.Dialect?

I assume it is one of the methods of NHibernate.Cfg.Configuration... Do you do this before building a session factory?

Could someone please give me an simple example?

Thanks in advance,

Damien Sawyer

adin05 · **Posted:** Thu May 19, 2005 3:30 am

There are plenty resources you can find to answer your question (Well, at least that's what I think :D ).

Here's a start:
http://wiki.nhibernate.org/display/NH/Quick+Start+Guide

Or maybe you've been there? For me, it is a clear simple walkthrough into using NH.

O yea, configuring NH can be done programmatically. Here's an example:

Code:

            this.AmetisConfiguration = new Configuration();

            //Setting Configuration Properties
            //*
            IDictionary props = new Hashtable();

            props["hibernate.connection.provider"] = "NHibernate.Connection.DriverConnectionProvider";
            props["hibernate.dialect"] = "NHibernate.Dialect.MsSql2000Dialect"; 
            props["hibernate.connection.driver_class"] = "NHibernate.Driver.SqlClientDriver";
            props["hibernate.connection.connection_string"] = "Server=127.0.0.1;Initial Catalog=Lexica;User ID=sa;Password=;";

            foreach( DictionaryEntry de in props )
            {
               this.AmetisConfiguration.SetProperty( de.Key.ToString(), de.Value.ToString() );
            }
            //*/

You'll need to set the appropriate value for the properties (well ... of course :D )

damiensawyer · **Posted:** Thu May 19, 2005 8:52 pm

Thanks - that's great!

Out of interest, I find it interesting that these are set by strings as opposed to being able to set properties on the configuration object via enums... Does anyone know if there was some reason for this? Maybe consistance with the Java parent?

Cheers

DS

sergey · **Posted:** Fri May 20, 2005 3:43 am

Yes, it was ported from Hibernate directly, works right, so nobody bothered to change it any further.

sirius b · **Posted:** Mon May 23, 2005 5:26 am

Probably also a future-proofing extinsibility measure. One couldn't guess all the obscure configuration properties that a RDBMS might need you to specify.