JSON export/import function about clover HOT 5 CLOSED

@jsgm Just to plan my activities, are you going to work on this? If you are busy, I'll put this on my todo list :=)

Sorry for the delay! A bit busy this week, feel free to put it in your todo list. In any case still looking forward to further contributions 😃

from clover.

Hi, jsgm, first of all thank you for the nice suggestion.

How to handle the conversion specially for bigger databases. Possible bottlenecks?

Regarding this point, I think that conversion should be performed in a cleaver way than simply calling json.Marshal on a document slice. I think that, in order to serialize large collections efficiently, documents should be progressively serialized and written to the exported file.

Use one just single file or multiple files. Maybe both options?

I think that it is fine to start by implementing a db.ExportCollection(collectionName, exportPath) function, which allow to export a single collection in a json file with the same name of the collection itself.
Then, by using this function, we could also implement an additional ExportDatabase(folderPath) function, exporting each collection inside a folder.
In the last case, we could also reason about an option for exporting the entire database in a single file (but this could also be added in a second step).

from clover.

@jsgm Just to plan my activities, are you going to work on this? If you are busy, I'll put this on my todo list :=)

from clover.

There is no rush, if you are interested in this ;=)

from clover.

There is no rush, if you are interested in this ;=)

Thanks for your patient. If there's no rush I can definitely go with this. Starting today!

from clover.