What is the best way to gather data from database based the cell selection of a DataGridView (C# .Net Windows Application)

By -

I have a DataGridView (C# .Net windows application) filled with more than 1000 rows also each row has a unique row id as well. If I select multiple cells then take the subdata from another table and display it in the same form.

I wrote the code inside the CellEnter event so whenever I select a cell, the event fires and takes the subdata from the database based on the unique id.

For Instance I have two tables: Table_Orders (OrderID primary key) ,Table_ShipmentDetails (OrderID Foreign Key). The DataGridView filled with Orders.Whenever i select cell,should display the shipment details.If i select multiple cells then find the OrderIDs and fetch the shipment details and compare them, if it is same then display else leave the information as blank

When i use CellEnter event my issues are

  1. If I select two cells in the same row, the event fires and fetches the same data two times from the database.

  2. If I select many cells together either with the mouse down or key down and with a slow connection, then the form will freeze and end up with restarting the program.

How can I avoid fetching the same data multiple times?

I tried to gather all the OrderIDs when entering the cell but couldn't find how to identify when the selection is completed for fetching the data together for all selected OrderIDs.

Can anyone help me to suggest an effective way to fix this issue?



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more