As we are getting closer to the release of the next dB version, I would like to understand if the new major release (that, in my understanding, will include both the current file-based approach and a db-based approach) will retain backwards compatibility with the current version in production.
Questions:
If we decide to use the file-based approach to store information, can we seamlessly migrate our existing data?
Will syncing with github be available in the dB version of the next major release?
(I understand there is an online version of the dB but I simply do not have the time to test different features that I use today to understand which of them are backwards compatible).
You can import a Markdown graph into Logseq DB, and there will be an option to export your DB graph to Markdown.
But if you have some kind of “switch” in mind that seamlessly switches the same graph between Markdown and Database modes, I have to disappoint you: that’s impossible from a technical standpoint. Each graph will have in one mode (Markdown, Org, or Database), which you choose when creating the graph.
Git uses plain text files, Logseq DB uses a SQLite file for storage. If you want to use Git with Logseq, you will have to stick to the plain text modes (Markdown or Org) of Logseq as Git can’t do merge conflict handling of SQL files.