StrataFrame Forum » StrataFrame Application Framework - V1 » Business Objects and Data Access (How do I?) » Effect of BO.Filter and BO.Save()

Effect of BO.Filter and BO.Save()

Edhy Rijo — Sat, 06 Jun 2009 18:44:24 GMT

I have a BO in which I edit several records based on the BO.Filter condition, so I do this:
[codesnippet]
1- Fill the BO with all records.
2- Apply filter #1 and modify some records.
3- Apply filter #3 and modify other records.
4- Remove BO.Filter and save the BO.
[/codesnippet]

Now when I call the BO.Save() will the Save() method do the following:
[codesnippet]
1- Scan all the BO records to see which one have been modified?
2- Or apply some internal filter to just save the modified records without looping all the BO records?
[/codesnippet]

I ask because originally the BO may have a couple of thousand records and need to know if the saving speed will be compromized in any way.

RE: Effect of BO.Filter and BO.Save()

Edhy Rijo — Sat, 06 Jun 2009 18:44:24 GMT

Thanks for the explanation. Now I know I don't have to worry about which BO.Filter is in effect in order to save all modified records.

RE: Effect of BO.Filter and BO.Save()

Trent L. Taylor — Sat, 06 Jun 2009 18:36:21 GMT

When looking at anything on the BO that deals with dirty records, the filter applied is irrelevant as the CurrenDataTable is used instead of the current view. Your applied filter will be left alone so there will not be any speed issues as the applied filter will be ignored for dirty records.

The Select() is used through ADO.NET on the data table to get any rows that have an added, modified, or deleted row state. The same logic is taken into account during a save. So you should not experience any performance issues in this regard. Just so you know, the current data table is enumerated (not the view) when checking any to see if a row needs to be checked for validation, so the applied filter is ignored there as well. In short, the save and row checking only looks at rows that have been modified, deleted, or added.