-
Hi All, So I ran into a glitch/undisclosed feature of budibase (See here and here) where the development data and the production data was not "in sync" and when I published new changes to the GUI a lot of the data in the couchDB instance was altered (back to the version in the developement db). There is very limitied information on the Fauxton/Mango process on quering the DB and working with data and finding tools that support couchDB is proving to be a challenge (Especially trying to connect in a docker environment.) Anyway, the short version of what I need is to "delete" newer entries back to previous versions where there were more data available. See the following: Query Result { I want the "live" data to be that of revision "4-6f2311e7deb22996d2b408936f40a691" as above. I can bank on the following statements being true:
It would be fantastic if it can be generalized to a "Which ever revision has the most data" statement. On a side note - any advice on how to "sync" the development environment data first before making this blunder again will be amazing. I beg and thank in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
Sorry missed to add all the technicals: |
Beta Was this translation helpful? Give feedback.
-
Hey @Zero2XIII It sounds like maybe you need to resolve conflicts in your data? There's a guide on doing that here: #7777 (comment) |
Beta Was this translation helpful? Give feedback.
-
Hi Guys, So I managed to resolve this with a very manual process. I created a view in Fauxton with the following: This gave me a list of records and when I open them up, you can see the conflict and decide which to keep. Key being opening up the entry and not relying on the visual que as that tends to come and go. They GUI for Fauxton is absurdly buggy, but I managed to resolve over a 100 conflicts by hand in doing so, which was a success... |
Beta Was this translation helpful? Give feedback.
Hi Guys,
So I managed to resolve this with a very manual process.
I created a view in Fauxton with the following:
function(doc) { if (doc['_conflicts'] && doc['Vin Number']) { emit(doc['Vin Number'], doc._id); } }
This gave me a list of records and when I open them up, you can see the conflict and decide which to keep. Key being opening up the entry and not relying on the visual que as that tends to come and go. They GUI for Fauxton is absurdly buggy, but I managed to resolve over a 100 conflicts by hand in doing so, which was a success...