search

MerginMaps / mobile

Mergin Maps mobile app 📲 Open QGIS projects and manage vector data on your phone, even offline 📶 (Android/iOS/Windows app)
https://merginmaps.com
GNU General Public License v2.0
299 stars 65 forks source link

Trigger support for gpkg in Input #1414

Closed HugoP27 closed 1 year ago

HugoP27 commented 3 years ago

Hi Lutra Team

I've set up a trigger for a gpkg in QGIS that updates one table in my geopackage when I update a separate table.

It works in QGIS, but unfortunately not in Input. Are gpkg triggers supported in Input?

Thanks

wonder-sk commented 3 years ago

Do you have a sample file that we could test?

In general triggers in gpkg should not be a problem in Input as such, but I think there may be a problem with syncing when there are some custom triggers (and you may start getting conflict files)

HugoP27 commented 3 years ago

Hi @wonder-sk Thanks for the swift response. I've attached the sample. The idea behind the trigger is that the user logs a weekly reading on the 3.1 Flowmeter Monitor layer which will have no labels or symbology, once logged the reading is populated to the latest_reading field in 3.Flowmeter using the trigger. Reason for this is that the user sees the latest reading when clicking on the flowmeter feature.

Thanks for testing this, if it will cause issues with syncing or not work in Input I will think of a workaround. trigger_sample.zip

PeterPetrik commented 1 year ago

this is geodiff issue https://github.com/MerginMaps/geodiff/issues/48, closing the ticket