StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PODataView.RowFilter Vs DataTable.Select() vs DataTable.Rows.Find()
primarykey
Id
2832304
data
AcceptedAnswerId
2864956
AnswerCount
2
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-05-14T06:43:46.700
FavoriteCount
21
LastActivityDate
2017-05-26T05:29:04.360
LastEditDate
2010-05-17T05:45:40.217
LastEditorUserId
213469
OwnerUserId
213469
ParentId
0
PostTypeId
1
Score
28
ViewCount
61329
LastEditorDisplayName
text
Body
Considering the code below: <pre><code>Dataview someView = new DataView(sometable) someView.RowFilter = someFilter; if(someView.count > 0) { …. } </code></pre> Quite a number of articles which say Datatable.Select() is better than using DataViews, but these are prior to VS2008. <a href="http://geekswithblogs.net/chrisfalter/archive/2006/08/15/88057.aspx" rel="noreferrer">Solved: The Mystery of DataView's Poor Performance with Large Recordsets</a> <a href="http://geekswithblogs.net/chrisfalter/archive/2006/08/04/87143.aspx" rel="noreferrer">Array of DataRecord vs. DataView: A Dramatic Difference in Performance</a> Googling on this topic I found some articles/forum topics which mention Datatable.Select() itself is quite buggy(not sure on this) and underperforms in various scenarios. On this(<a href="http://msdn.microsoft.com/en-us/library/ms971481.aspx" rel="noreferrer">Best Practices ADO.NET</a>) topic on msdn it is suggested that if there is primary key defined on a datatable the findrows() or find() methods should be used insted of Datatable.Select(). This article <a href="http://www.windowsitpro.com/article/aspnet2/choose-wisely.aspx" rel="noreferrer">here</a> (.NET 1.1) benchmarks all the three approaches plus a couple more. But this is for version 1.1 so not sure if these are valid still now. Accroding to this DataRowCollection.Find() outperforms all approaches and Datatable.Select() outperforms DataView.RowFilter. So I am quite confused on what might be the best approach on finding rows in a datatable. Or there is no single good way to do this, multiple solutions exist depending upon the scenario?
Tags
<.net><visual-studio-2008><performance><ado.net><datatable>
Title
DataView.RowFilter Vs DataTable.Select() vs DataTable.Rows.Find()
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USAseem Gautam
UserOwnerUserId
1. USAseem Gautam
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
CommentsPostId
1. COThank you for the reward!
 singulars
 PostPostId
 PODataView.RowFilter Vs DataTable.Select() vs DataTable.Rows.Find()
 UserUserId
 USthmshd

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.