Lazy mode is handy to deal with large datasets, instead of loading the entire data, small chunks of data is loaded by invoking corresponding callbacks everytime paging, sorting and filtering happens. Sample belows imitates lazy paging by using an in memory list.
- It is also important to assign the logical number of rows to totalRecords by doing a projection query for paginator configuration so that paginator displays the UI
- assuming there are actually records of totalRecords size although in reality they aren't as in lazy mode, only the records that are displayed on the current page exist.
-
-
Lazy loading is implemented by handling pagination and sorting using page and sort events by making a remote query using the information
- passed to the events such as first offset, number of rows and sort field for ordering. Filtering is handled differently as filter elements are defined using templates, use
- the event you prefer on your form elements such as input, change, blur to make a remote call by passing the filters property to update the displayed data. Note that,
- in lazy filtering, totalRecords should also be updated to align the data with the paginator.
-
-
Here is a sample paging implementation with in memory data, a more enhanced example with a backend is being worked on and will be available at a github repository.
Filtering is enabled by defining a filter template per column to populate the filters property of the DataTable. The filters
property should be an key-value object where keys are the field name and the value is the filter value. The filter template receives the column properties
@@ -601,6 +544,143 @@ data() {
<Column field="color" header="Color"></Column>
</DataTable>
+
+
+
Lazy Loading
+
Lazy mode is handy to deal with large datasets, instead of loading the entire data, small chunks of data is loaded by invoking corresponding callbacks everytime paging, sorting and filtering happens. Sample belows imitates lazy paging by using an in memory list.
+ It is also important to assign the logical number of rows to totalRecords by doing a projection query for paginator configuration so that paginator displays the UI
+ assuming there are actually records of totalRecords size although in reality they aren't as in lazy mode, only the records that are displayed on the current page exist.
+
+
Lazy loading is implemented by handling pagination and sorting using page and sort events by making a remote query using the information
+ passed to the events such as first offset, number of rows and sort field for ordering. Filtering is handled differently as filter elements are defined using templates, use
+ the event you prefer on your form elements such as input, change, blur to make a remote call by passing the filters property to update the displayed data. Note that,
+ in lazy filtering, totalRecords should also be updated to align the data with the paginator.
+
+
Here is a sample paging implementation with in memory data, a more enhanced example with a backend is being worked on and will be available at a github repository.
Rows can be expanded to display additional content using the expandedRows property with the sync operator accompanied by a template named "expansion". row-expand and row-collapse are optional callbacks that are invoked when a row is expanded or toggled.
+
+
The dataKey property identifies a unique value of a row in the dataset, it is not mandatory in row expansion functionality however being able to define it increases the performance of the table signifantly.