Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > LLBLGen Pro Runtime Framework> Limiting Columns to Return
 

Pages: 1
LLBLGen Pro Runtime Framework
Limiting Columns to Return
Page:1/1 

  Print all messages in this thread  
Poster Message
DaveR
User



Location:

Joined on:
15-Jun-2004 16:37:10
Posted:
43 posts
# Posted on: 16-Aug-2005 00:34:18.  
I have a view for which I only want to retrieve certain columns, for two reasons:

1. Efficiency. Some of the columns are text fields that might be very long; I don't want to retreive them until I need them.

2. Filtering duplicates. SQL Server does not allow DISTINCT queries if there are text columns.

The ideal scenario would be to indicate to the (SelfServicing) collection which fields to retrieve. If a field is accessed that was not retrieved, it would be retrieved on demand. I realize LLBLGen doesn't have such a feaure, but it might be useful.

I know that I can built a custom dynamic list and populate a DataTable using TypedListDAO() but this is not very convenient.

At this point I will probably just define another view that contains only those fields I am interested in, and use this separate view for the DISTINCT query. But I was hoping there was a better way.

Is there?
  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37804 posts
# Posted on: 16-Aug-2005 08:29:58.  
Not at the moment. In the upcoming 1.0.2005.1 upgrade, you can map an entity to the view and exclude certain fields, for example your textfields. I'll see if there is time to also add this for views.

Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.