blocks|key|789532|text|一般而言，对数据库进行过滤更有效率，因为数据库不仅要返回的数据更少，而且通常要处理的数据也更少(例如，它可以使用索引来减少要处理的记录量)。此外，在大多数基础设施中，数据库与客户端不在同一台服务器上，因此还存在返回未过滤数据所涉及的其他资源。一般来说，需要处理的数据越多，在数据库上进行过滤的效率就越高。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|789533|但很明显，如果应用程序手头已经有数据库首先必须查询的信息，那么也可能存在使代码/客户端中的过滤更有效的情况。|789534|但所有这些都非常模糊，最终它取决于您的应用程序。如果你说你有一个数据网格，而用户对同一静态数据的过滤器做了很多更改，那么在数据库上过滤将导致数据库服务器上大量不必要的流量和工作负载，而未过滤的缓存在客户端上的数据将提高效率。|789535|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

In general, filtering on the database is more efficient, because the database not only has less data to return, but normally it has also less data to transact (eg. it can use indexes to reduce amount of records to be processed). Furthermore, in most infrastructures is the database not on the same server as the client and therefore there are also other resources concerned from returning unfiltered data. Generally, the more data has to be processed, the more efficent is filtering on the database.

But there could be clearly also circumstances that makes filtering in code/client more efficient, mostly if the application has information already at hand that the database first must query. 

But all this is very vague, in the end it is dependent on your application. If you say you have a datagrid and the user makes many changes to filters concerning the same static data, filtering on the the database will lead to a lot unnecessary traffic and workload on the db server wheras unfilterd cached data on the client would increase efficiency.

blocks|key|2857386|text|好了，您已经从数据库中提取了一个数据子集，并将其呈现给了用户。人世间万事大吉。现在，讨厌的用户想要对数据进行进一步的过滤。假设我们不是通过游标之类的方式访问大量数据集，那么数据已经在内存中了。我很想在那里过滤它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2857387|如果数据没有快速变化，并且存在一定程度的过时的可能性是可以接受的，那么就没有充分的理由返回数据库来提取已有数据的子集。您已经通过网络提取了一次数据，为什么还要再做一次呢？|2857388|如果数据确实需要更新，那么忘记我刚才所说的一切，去向DB索要它。|2857389|这个想法可能介于数据访问层和数据访问层之间。在这里，您将监视数据年龄，并确保即使用户在几个小时内不断更改相同数据集的筛选，也会从数据库中定期刷新。对过滤数据的请求也应该呈现给这一层，这样你的应用程序就不会察觉到它是实际从内存中获取的，还是只是从内存中获取的。如果你认为其中一种方法(内存或数据库)实际上总是更好的，那么这种关注点的分离将对你继续前进很有帮助，因为你将能够改变底层代码并保持你的应用程序不变。|2857390|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Okay, so you've pulled down a subset of data from the database and you have presented it to the user. All is great in the world. Now the pesky user wants to apply further filtering to the data. Assuming that we're not accessing massive data sets through cursors and the such like, then the data is in memory already. I'd be very tempted to filter them there.

Provided the data isn't changing rapidly and that the chance of a certain degree of staleness is acceptable then there's no good reason to go back to the database to extract a subset of what you already have. You've already pulled the data over the wire once, why do it again.

If the data does need to be bang up to date then forget everything I've just said and go ask the DB for it.

The idea is probably somewhere in between that would be marshalled by your data access layer. Here you'll monitor data age and ensure that even if the user just keeps altering the filtering of the same data set for hours, it's periodically refreshed from the database. The request for the filtered data should also be presented to this layer, that way your app is blind to whether it's actually fetched or just served from memory. That separation of concern will stand you in good stead moving forward should you ever decide that one or the other approach (memory or database) is actually always better as you'll be able to change the underlying code and leave your app unchanged.

blocks|key|1747392|text|肯定是在过滤现有的数据集合。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1747393|有几个解决方案来过滤现有的DataGridCollection，但在我看来，最好的解决方案是那些只使用标准WPF+DataGrid控件的样式，而不发明新的继承DataGird类型或依赖于另一个第三方控件的解决方案。下面是我找到的最好的解决方案：|offset|length|style|CODE|1747394|我个人使用的|1747395|选项1：Automatic+WPF+Toolkit+DataGrid+Filtering|unordered-list-item|1747396|Option+2：Auto-filter+for+Microsoft+WPF+DataGrid|1747397|1747398|entityMap|0|LINK|mutability|MUTABLE|url|http://www.codeproject.com/KB/WPF/DataGridFilterLibrary.aspx|1|http://www.codeproject.com/KB/WPF/wpffiltering.aspx^0|0|1L|8|27|8|0|0|4|14|0|0|9|12|1|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@$D|11|E|12|F|G]|$D|13|E|14|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|15|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|16|8|@]|9|@$D|17|E|18|1|19]]|A|$]]|$1|M|3|N|5|L|7|1A|8|@]|9|@$D|1B|E|1C|1|1D]]|A|$]]|$1|O|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]|X|$5|S|T|U|A|$V|Y]]]]

Definitely filtering the existing data collection.

There are several solutions to filtering existing DataGridCollection, but in my opinion, the best solutions are the ones which uses only styles with the standard WPF <code>DataGrid</code> control without inventing a new inherited <code>DataGird</code> type or depending on another third-party control. The followings are the best solutions I found:

<ul>
<li>Option 1: which I personally use: <a href="http://www.codeproject.com/KB/WPF/DataGridFilterLibrary.aspx" rel="nofollow">Automatic WPF Toolkit DataGrid Filtering</a></li>
<li>Option 2: <a href="http://www.codeproject.com/KB/WPF/wpffiltering.aspx" rel="nofollow">Auto-filter for Microsoft WPF DataGrid</a></li>
</ul>

While filtering existing data of a datagrid, what is more efficient:

<pre><code>- filtering the existing data collection OR
- querying database with filter clauses
</code></pre>

Filtering a datagrid - efficient way

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在过滤数据网格的现有数据时，哪个更有效：- filtering the existing data collection OR- querying database with filter clauses

问过滤数据网格高效的方式
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问过滤数据网格高效的方式EN