CurrentData Table v.s. Collection of objects?


Author
Message
Ben Hayat
Ben Hayat
Advanced StrataFrame User (568 reputation)Advanced StrataFrame User (568 reputation)Advanced StrataFrame User (568 reputation)Advanced StrataFrame User (568 reputation)Advanced StrataFrame User (568 reputation)Advanced StrataFrame User (568 reputation)Advanced StrataFrame User (568 reputation)Advanced StrataFrame User (568 reputation)Advanced StrataFrame User (568 reputation)
Group: Forum Members
Posts: 374, Visits: 1.2K
I meant to ask this question in the class and missed it. Maybe it's best to ask here so others get the answer as well;



SF creates an strongly typed version of a data row when BO Mapper maps it to the data row. Now in order to get a series of those rows, why doesn't SF create a collection of those rows rather using ADO.Net CurrentData Table as a collection of those rows. This seems to me a hybrid form of dealing with single record and a set of records.



If SF would use collection of BOs, then any control that supports collection can naturally list those items.

And it would be ready for LINQ right out of the box!



Thanks!

..ßen
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search