mschoema / move Goto Github PK

Database table has 1 trip, which I copied to a new schema, it appears there is an insert requirement or trigger? Since the 'public' schema is referenced but the query specifies 's1'

car_id trip_id trip
1 1 [010100000000000000000000000000000000000000@2012-01-01 08:00:00+00, 010100000000000000000000400000000000000000@2012-01-01 08:10:00+00, 01010000000000000000000040666666666666FEBF@2012-01-01 08:15:00+00]

Query #1
select trip from s1.trips_test_001

Log message
2022-06-14T10:57:41 INFO Running Query: select trip from s1.trips_test_001
2022-06-14T10:57:41 INFO Query return types: tgeompoint

General log
2022-06-14T10:57:43 WARNING Feature type or srid for geom of "public"."move__tpoint_0_4ee6b0e8377344cc9c730e74772a096c" could not be determined or was not requested.

Creating and removing materialized views has to be done carefully.

Below are different use-cases that need to be handled:

• Multiple QGIS projects from the same user on the same database
• Mulitple QGIS projects from different users on the same database

Currently, both cases work if all the projects working on the same database have different names.
This is not ideal, as we cannot require different users to know each other's project names.

Potential ideas:

• Use a unique name per user and combine it with the project name.
• Use a unique id per project instead of the project name.

Modify the "Refresh layers" function to only refresh the materialized view of the currently selected layer.
This will speed up the operation as it is usually not useful to refresh all layers every time.

Add different info/warning/error popups or labels to the plugin.

Example use-cases:

• Send an error if the project name is empty
• Send an error if the query failed
• Send a warning if the query did not contain any temporal values