According to this post, when the now beta DB version is formally released, it will include support for both DB and MD back-ends. User can selects which back-end to use when create a new graph.
AFAIK yes. You can use the MD version to your hearts content and just ignore the DB version. Although I’m curious as to why (other than synchronisation) the DB version is a struggle for you.
You could in theory just use it as though it were just the MD version pretty much. Although you’d be missing out on NewTags of course
I don’t want to get into a lot of detail here because this really isn’t the place for it, but the way things like TODOs are handled is very different and unintuitive to me. Lists of selectable properties and statuses rather than just typing exactly what I want when and where I want it breaks me right out of my flow and I feel like I’m constantly running into cage walls. Databases and free-form text are just very different structural paradigms, and my brain only plays well with one of them.
1 Like
You may want to check out Silverbullet – I’ve been migrating away from Logseq over to it and it’s been a wonderful experience.
it takes a bit to get used to and you have to be comfortable writing some Lua code, but once you’re in the swing of things with it it really is great. Instead of fitting your workflow into whatever Logseq thinks it should be, you can tailor Silverbullet into what fits you best.
1 Like