I am in no way urging the NH team to work on it. I am asking in what
way I would help.
On Jul 19, 2:42 am, Fabio Maulo wrote:
> QueryOver is incomplete because we are working on it and SetMaxResult(),
> SetCachable(), etc etc. are less important than others things we would do
> in QueryOver.Thos
QueryOver is incomplete because we are working on it and SetMaxResult(),
SetCachable(), etc etc. are less important than others things we would do
in QueryOver.Those methods are not there because we are waiting a little bit
more to consider QueryOver ready for production.
2009/7/18 Canton
>
> Th
Thanks for work.
I would like to know what's the strategy for completing the interface.
By completing the interface, I mean those SetMaxResult(), SetCachable
(), UniqueResult(), Future(), etc.
Shall we expose each of those methods in IQueryOver? or instead
expose a GetCriteria() API if one want
For mappings we are using classes generated from XSD.For strongly typed
cache configuration:
http://fabiomaulo.blogspot.com/2009/07/nhibernate-configuration-cache.html
2009/7/18 mcintyre321
>
> Hi there,
>
> I've just been reading Fabio's posts on configuring NH3, and had a
> couple of thoughts.
Hi there,
I've just been reading Fabio's posts on configuring NH3, and had a
couple of thoughts. With 2.x I've been running Linq2XSD against the
mappings xsd to generate a class model of the mapping schema, and then
using this model to create mappings using c#.
I was thinking this would be a han
