Hey,
I have a scenario where we do not know the column names or data types until run-time.
We would like to be able to use data virtualization in this scenario. Basically we construct the sql statement at run-time once we query the table for its metadata (columns). We could add an orderby, since the VirtualQueriableCollectionView needs one.
The question is: without pre-loading everything from the table into the VirtualQueriableCollectionView (which would defeat the purpose of this view) how do we wire our sql statement into a VirtualQueriableCollectionView.
We studied this example: GridView -> Databinding -> Various Data Sources example -> Dynamic Data
This example solves the issue of dynamically generating columns that aren't hard-coded in a model, but doesn't show how one could hook this type of solution into data virtualization.
I have a scenario where we do not know the column names or data types until run-time.
We would like to be able to use data virtualization in this scenario. Basically we construct the sql statement at run-time once we query the table for its metadata (columns). We could add an orderby, since the VirtualQueriableCollectionView needs one.
The question is: without pre-loading everything from the table into the VirtualQueriableCollectionView (which would defeat the purpose of this view) how do we wire our sql statement into a VirtualQueriableCollectionView.
We studied this example: GridView -> Databinding -> Various Data Sources example -> Dynamic Data
This example solves the issue of dynamically generating columns that aren't hard-coded in a model, but doesn't show how one could hook this type of solution into data virtualization.