Is there a way in DAL2 to determine properties/fields/columns in SELECT clause?
Suppose I have a nvarchar(max) field in my database table/info object:
string LongDescription //nvarchar(MAX)
Suppose I also have a million Articles records in my database.
When selecting a single record, I want to hydrate all the database columns in the articleinfo object
but when I execute a SELECT * FROM Articles I do NOT want to have the nvarchar(max) column in my SELECT clause. For example to get a list of all articles.
This will lead to huge performance bottlenecks.
I'm curious about your thoughts on this