I’ve been a logseq user for 6 years (imagine the graph I have!). I’m an academic researcher and I based my entire project development on logseq. Moreover! I recommended logseq to everyone I know in the field.
I just can’t believe that when, last week, I tried to update to the latest version, I came to know that there is a database version and that the migration tool MD –> DB does not work!! Come on!! The most important feature of logseq is to connect info when you have A LOT OF INFO.
When I tried to do the import, namespaces are not well-imported, issues with zotero, issues with queries, the entire structure got broken, etc.
The new version was made thinking just in the future, and there was no consideration on those who had huge important graphs. This undermines the trust in this project.
Please, let us make a consistent migration tool for overcome this tremendous issue.
You know you can keep using the non-DB version of Logseq indefinitely? A lot of other users are not into the idea of moving away from the plain md files: Is anyone planning to use OG version indefinitely?
It’s a pity that the developers switched the whole premise of the project like this, but at least there’s a low effort/semi-abandoned version available at GitHub - logseq/og: Logseq og (file version) · GitHub that is supposed to get some updates at least from time to time.
Same here. I can see there are some good ideas and some nice functions in the DB version.
However the migration tool is a disaster. The whole structure is destroyed.
I guess I can only wait for a usable tool, or just keep using the old version.
