Thanks. I see. But how adding a new dialect can solve the issue when writing HQL we don't know about a DB we are using. Extending dialect we have to do it for each supported DB and instead of using default NH dialect we have to force to use customised dialects for each DB.
2009/6/3 Fabio Maulo <[email protected]> > Take a look > here<http://nhibernate.svn.sourceforge.net/viewvc/nhibernate/trunk/nhibernate/src/NHibernate/Dialect/MsSql2008Dialect.cs?revision=4056&view=markup> > . > > As you can see the MsSql2008Dialect is only an extension > of MsSql2005Dialect registering some new column type and > registering/overriding some functions. > You can do the same in your project. > After that you can use you own dialect: > <property > name="dialect">YourCompany.NHExtensions.YourMsSqlDialect, > YourCompany.NHExtensions </property> > > > 2009/6/1 Dmitiry Nagirnyak <[email protected]> > >> You can register the corresponding function in your dialect extension >>> (your custom dialect inherited from standard). >> >> Don't you mind to give a little more background please (sorry I'm really >> new to NH)? >> >> >> > > > -- > Fabio Maulo > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
