As we are in the Temporal Controller Saga and I'm about to migrate some data in temporal tables in MSSQL for some testing, I was wondering if there was a way to properly use the virtual controller with virtual layer more directly.
The optimal way to do this would be to have the values of the controller exposed somehow in the query, either by adding expression support to form the virtual layer query or through some other mean.
As a workaround in the meantime I would assume that one would have to use a virtual layer to query the full data set (both active and in the history table) to perform the time control filtering, instead of letting the provider do the work by modifying the query.
Additional context
Though not natively in postgress many providers have temporal database/tables and I was thinking that we could leverage some functions of qgis for more direct support
Feature description.
As we are in the Temporal Controller Saga and I'm about to migrate some data in temporal tables in MSSQL for some testing, I was wondering if there was a way to properly use the virtual controller with virtual layer more directly.
The optimal way to do this would be to have the values of the controller exposed somehow in the query, either by adding expression support to form the virtual layer query or through some other mean.
As a workaround in the meantime I would assume that one would have to use a virtual layer to query the full data set (both active and in the history table) to perform the time control filtering, instead of letting the provider do the work by modifying the query.
Additional context
Though not natively in postgress many providers have temporal database/tables and I was thinking that we could leverage some functions of qgis for more direct support