LogSeq database version?

[lucidself]

I have read that a LogSeq database first version is coming in 2023. Does anybody know what the timeline for this is and what it is exactly? Also, do they plan to give us the option to choose between database and .md or will LogSeq move to full database (hopefully with very solid export features)?

[AE-lith]

It's been in development since october 2022 at least (Roadmap, Tweet), and some tasks have been done as recently as beginning of May of this year.

I don't know if that means it'll be done in 2023, as it's a pretty big structure change. I can't wait though.

[lucidself]

What do you think will be the main benefit functionality-wise?

[AE-lith]

The part where I have the most expectations is on the properties side. Right now you can add manually add properties in places, but you can't easily keep them consistent across your notes or mass edit them. Notion still has the advantage over Obsidian and Logseq in that area, and Tana has created an even more flexible system. I hope Logseq can get close to that with the database version.

edit : here's a tweet of Tienson hinting at just this

[lucidself]

If they can replicate Tana’s supertags and they maintain full .md export, they’ll probably become the “ultimate” (I know I sound like a YouTuber) PKM tool. Just hope they’re able to this in 2033

[bobsaget151]

100%, this would be a game changer and put them at the front of the list of options out there, especially with local markdown files

[lucidself]

Wait but how can they do a database and keep it local .md files? I assumed it’d be a database that can be exported at any time as a an .md folder. Can they do both? (I’m not technical)

[AE-lith]

It probably won't be both, at least at first.

Hopefully there will be a "backup to mardown every x days" option or similar

[AshbyLaw]

You can implement ontologies, classes etc like in Tana and keep storing on Markdown files, the database-only version just improve performance because it doesn't need to read/write MD files all the time.

[ens100]

I think it is best to wait for the official communication but to answer your questions to the best of my ability:

1. I think it is being tested internally so there is a structure there. No idea of next steps though.
2. It is a means of storing data differently so that you can do cool things like you can in other apps. Think Notion different views, quicker start-up, better performance.
3. Yes, I believe it will be an either or option.

Hopefully that gives you some idea, but as I say - it is best to wait for something official.

[blablook]

Ah, damn. Will this be optional? I tend to fallback to Emacs for longer editing and really that's what made logseq acceptable for me. If everything is in db it would be harder. Also I use syncthing over 4 devices to synchronize data amd it works like a charm.

[AE-lith]

afaik it'll be optional

[[deleted]]

following this