Yes!! throw the SP and use HQL to return classes instead a DTO, then you can create the DTO in RAM using a simple LINQ.Select
On Mon, Jul 12, 2010 at 11:24 AM, Mike <[email protected]> wrote: > Hello, > I have a situation where I have a complex stored procedure returning > records for a grid. At this point I do not have a business case to > rewrite this Stored Procedure using NHibernate, so I am calling it as > a named query and populating a DTO. This is working great. > > However, now I need to supplement my DTO with my domain logic to add > another column to the grid. I am still hoping to avoid having to > rewrite this Stored Procedure. Initially, I was returning my DTO, > using LINQ to extract an array of IDs, and calling an NHibernate query > where my record ID's where in that list. This worked great until I > tried to pull all of the records and hit the limit of allowed > parameters in SQL Server 2005. > > Are there any creative ways I can accomplish this successfully? > Thanks! > > -- > 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]<nhusers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > > -- 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.
