Davor Racic
Davor Racic
Ok, that was our first idea, to change pg type to REAL and force init again. Thanks!
@wonder-sk but we have the same error using real. So changeset is formed correctly but SQL uses wrong representation. ``` mergin-db-sync-tc | Warn: CONFLICT: update_nothing: mergin-db-sync-tc | { mergin-db-sync-tc |...
Update, float8 works... But still strange. Is that extra WHERE necessary at all?
We also noticed this, especially in mountain areas. Shouldn't streaming use only GPS location points that are within accuracy threshold? Comparing with some other solutions - it would be useful...
@jacob314 i have a ready and simple fix for this... I implemented dual-mode completion for custom commands by modifying `useCommandCompletion.tsx` to check if a slash command is a custom command...
Ok, I will make a PR as a workaround for this until the new version with new py-client is ready.
I really don't know. Now i'm stopping dbsync container during work hours, but again: ``` == starting mergin-db-sync daemon == version 2.1.1 == Using config file: /config/config-tc.yaml Logging in to...