Refreshing a data provider won't update items when the item instance is not the same
See original GitHub issueWhen refreshing a Grid
data provider, if the item instances change (e.g. when fetched from a database), rows are not updated if a column value has changed.
Demo: GridRefreshAll.java
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Refreshing item in DataProvider for Grid, and implementing ...
The DataProvider::refreshItem method used by Grid and other widgets advises two alternate ways for the widget to identify which of the contained ...
Read more >Troubleshoot refresh scenarios - Power BI - Microsoft Learn
This article provides ways to troubleshoot issues with refreshing data within the Power BI service, for various data sources and conditions.
Read more >Showing a List of Data with Data Providers - Vaadin
Notifying the Data Provider About Item Changes DataProvider has two methods for this purpose, refreshAll and refreshItems . Example: Using the ...
Read more >Refresh Data Sources - Tableau Help
Not every connection will behave in the same way. There are three primary connection types: Live Connection, Extract, and Published Data Source. The...
Read more >Refreshing the Asset Database - Unity - Manual
It looks for changes to the Asset files, and then updates the source Asset Database · It imports and compiles code-related files such...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
As a workaround, you can do
grid.setDataProvider(grid.getDataProvider());
.I think it’s a bug then, since when overriding the
DataProvider::getId
it shouldn’t rely onequals
/hashCode
but on the ID. Certain frameworks (e.g. Spring Data with projections, or Blaze Persistence with entity views) might provide DTO instances created dynamically and you can’t really override theirequals
/hashCode
methods.