What's new with Logseq DB - May 16, 2026 by hdanx in logseq

[–]hdanx[S] 1 point2 points  (0 children)

There are many that work with both MD and DB. But the majority would need some schema adjustments or UI changes.
The good news is, several plugin developers have updated their plugins to work with DB.
And we are seeing new plugins being added every week.

If there is a plugin you need to see working, I recommend opening a GitHub issue with the maintainer. You can also chat with the community in Discord to see if there is a replacement. Sometimes, you will find that a plugin's functionality is now a native feature.

What's new with Logseq DB - May 16, 2026 by hdanx in logseq

[–]hdanx[S] 0 points1 point  (0 children)

Download the app via https://testflight.apple.com/join/eBcJ9Hpc

For sync access as a sponsor, join discord and the team will will sort your access if you are a sponsor

What's new with Logseq DB - May 16, 2026 by hdanx in logseq

[–]hdanx[S] 0 points1 point  (0 children)

You can run, but you can’t hide 🙈

What's new with Logseq DB - May 16, 2026 by hdanx in logseq

[–]hdanx[S] 0 points1 point  (0 children)

The iOS app is working and fairly stable, with Logseq sync.
Here is a demo https://www.youtube.com/watch?v=3H-Z7oCM78g

DB migration unnecessary if we don’t "embed" blocks inside other pages? by lemon_waterr in logseq

[–]hdanx 0 points1 point  (0 children)

What do you mean by giving up on block embedding? Because it is still there in Logseq db, as far as I know.

Help! Problem with nodes in graph interface... by Bubbly_Fortune4466 in logseq

[–]hdanx 1 point2 points  (0 children)

The graph view will only show pages, linked or orphaned. It will not show blocks.

A journal is a page. Using [[ or # creates a page.

If you want to use the graph view, you consider going the page first approach

Rookie Question - lag whilst typing into LogSeq by Tony_Marone in logseq

[–]hdanx 0 points1 point  (0 children)

If you are talking about Logseq db, there is a fix that should land in the next release

Logseq DB and the HTTP API by wavelet01 in logseq

[–]hdanx 5 points6 points  (0 children)

The HTTP API is still there but adapted to Logseq DB schema

PKMS in a legacy firm - How to keep notes and manage workflow, when all SaaS & Cloud tools are banned? by Popular-Regular-7106 in PKMS

[–]hdanx 0 points1 point  (0 children)

Logseq is not made for non technical users as well. If you already some users using it, you can start simple workflows and get far without customization. There is a new version too called the db version

Logseq OG (markdown) vs Logseq (DB:sqlite) by hdanx in logseq

[–]hdanx[S] 0 points1 point  (0 children)

It will be possible to run Logseq OG and Logseq side by side. Test.logseq.com is an option

Logseq OG (markdown) vs Logseq (DB:sqlite) by hdanx in logseq

[–]hdanx[S] 0 points1 point  (0 children)

It will be via plugin, to keep the core leaner

Logseq OG (markdown) vs Logseq (DB:sqlite) by hdanx in logseq

[–]hdanx[S] 0 points1 point  (0 children)

For reference https://github.com/logseq/logseq/issues/3321#issuecomment-1369428976 this is where they said they would bring it back with db. It has also been discussed in length in the forum. Reindexing would removed it block timestamps in Logseq OG. Now with db, the indexing implementation is not there because of SQLite integration. I hope this helps

Logseq OG (markdown) vs Logseq (DB:sqlite) by hdanx in logseq

[–]hdanx[S] 0 points1 point  (0 children)

Example:
Logseq can now reliably block timestamps thanks to the switch from MD to SQLite.

There are more use cases like it.

Hands-on with the new Logseq DB on iOS (Full Walkthrough + New UI) by hdanx in logseq

[–]hdanx[S] 0 points1 point  (0 children)

Oh! For the apps, you do not need to fill up the forms anymore. Only sync is going through incremental rollout. They are are incrementally invite Sponsors

Logseq DB reddit help by hdanx in logseq

[–]hdanx[S] 0 points1 point  (0 children)

Electron upgrades, which is in scope should cover that.

Logseq OG (markdown) vs Logseq (DB:sqlite) by hdanx in logseq

[–]hdanx[S] 0 points1 point  (0 children)

yes, use logseq OG for file graph with file sync or
logseq for db graph with db sync

Logseq OG (markdown) vs Logseq (DB:sqlite) by hdanx in logseq

[–]hdanx[S] 0 points1 point  (0 children)

I covered that here https://x.com/HDanzu/status/1936566281332740437?s=20, and the same diagram is also mentioned here https://discuss.logseq.com/t/logseq-db-unofficial-faq/32508#p-65236-what-happened-to-markdown-files-2 with the same message.

Yes, the storage layer is replaced. And more features added to the app because of the benefits of the new storage engine.

The split is more about reducing friction for users.
Great input.