nhibernate-criteria

How can I write the following SQL using Criteria: select b.Name as Batch, b.Capacity as Capecity, a.tStudent as Admit, (b.Capacity-a.tStudent) as Availabe from ( SELECT count(Id) as tStudent, BatchId FROM [dbo].[Student] group by BatchId) as a left join [dbo].[Batch] as b on a.BatchId = b.Id To use NHibernate, to produce query like this: SELECT ... FROM ( SELECT ... ) AS a .. We have to options: Map the sub-select as an Entity. create raw SQL query The first option would mean to create some view , and map it as an Entity. If we do not like view (or cannot create it) we can use the power of

Using NHibernate 2.1, I'm trying to project an entity and its child collection into a DTO. My entity looks like this.. public class Application { public int Id {get;set;} public string Name {get;set;} public List<ApplicationSetting> Settings {get;set;} // A bunch of other properties that I don't want in the DTO } public class ApplicationSetting { public int Id {get;set;} public string Name {get;set;} public string Code {get;set;} // A bunch of other properties that I don't want in the DTO } My DTO looks like this.. public ApplicationDto { public int Id {get;set;} public string Name {get;set;}

I am currently dynamically constructing queries like so: QueryOver<Base, Base> q = QueryOver.Of<Base>(); if (foo != null) q = q.Where(b => b.Foo == foo); // ... Now there are multiple mapped subclasses of Base (e. g. Derived ) which I want to filter on, basically something like: if (bar) q = q.Where(b => b is Derived); // does not work or: if (bar) q = q.Where(b => b.DiscriminatorColumn == 'derived'); // dito How do I best achieve that, preferably - but not neccessarily - in a type-safe way? Can this be done using LINQ, too? This is not intuitive, but the following should work fine (QueryOver)

nHibernate3; retrieving 4xxx records out of an EAV data schema. When nHibernate, or .NET, goes to initialize those collections for the first time, we're seeing a severe penalty. Subsequent calls appear to perform more efficiently. Running the same queries in SQL Server Management Studio result in expected quick return times. Using Fluent and runtime mapping instead of .hbm.xml; curious if serialized mapping would help here? nHibernate Profiler and log4net logging didn't seem to give me much to go on. A total of something like 140,000 entities are hydrated in this process. Attached a screenshot

Consider two entities Person which has a one-to-many collection Vehicles public class Person { public IList<Vehicle> Vehicles { get; set;} } public class Vehicle { public string Name { get; set;} public Person Owner { get; set; } } I display a grid of Persons having vehicle and show the name of the first vehicle in the grid. The grid is paginated. I use the following criteria to fetch the data I have a criteria for loading data for a grid view as var criteria = DetachedCriteria.For<Person>() .CreateAlias("Vehicles","vehicle", JoinType.InnerJoin) .SetResultTransformer(new