4
submitted 1 week ago by [email protected] to c/[email protected]

Logseq DB Unofficial FAQ

https://discuss.logseq.com/t/logseq-db-unofficial-faq/32508

WARNING: Logseq DB is still in alpha. Use only at own risk of losing data. This post is for people who have questions about the new database (DB) version of Logseq. For the official announcement about the database version, see this post from April...

#logseq #pkm [email protected] @[email protected]

you are viewing a single comment's thread
view the rest of the comments
[-] [email protected] 1 points 1 week ago

Yeah, but the source of truth will be the sqllite db. So it will have to be synced over syncthing, rclone... Lot of, for my use case, unnecessary copying of binary blob

I totally see how pure files can be a PITA for collaboration management but I don't collaborate, I just want to have the same thing across different places

[-] [email protected] 2 points 6 days ago

Not necessarily and also not how I understood the post. It's certainly an option and an ergonomic one at that. So it's not unthinkable they go that route.
But you could also offer a choice of backend when creating a new graph. Text-based allows you to sync you files between devices, e.g. via source control, and offer asynchronous collaboration this way, while the DB-based approach forfeits source control and opts to keep its data consistent through simultaneous edits from multiple clients itself.
But managing that consistency takes quite considerable effort, as we're witnessing, for no clear advantage, just a tradeoff. And I at least think it would be a shame to let the work already gone into the development of the text backend go to waste. I think the devs might share that opinion.

[-] [email protected] 1 points 6 days ago

From the link in the OP

Both the original Markdown (MD) based version of logseq and the DB version use an internal database when you are using the app. The difference is that, in the MD version, the files are always canonical. In the DB version, while you will can export to markdown files, the database version is always canonical.

But maybe that's temporary, in the older link from my comment nothing suggests this is the design goal

this post was submitted on 01 Aug 2025
4 points (100.0% liked)

Logseq

817 readers
4 users here now

Logseq is a knowledge management and collaboration platform. It focuses on privacy, longevity, and user control. It is Free Libre Open Source Software (AGPL-licensed).

Logseq offers a range of powerful tools for knowledge management, collaboration, PDF annotation, and task management with support for multiple file formats, including Markdown and Org-mode, and various features for organizing and structuring your notes.

Logseq's Whiteboard feature lets you organize your knowledge and ideas using a spatial canvas with shapes, drawings, website embeds, and connectors. You can visually group and link your notes and external media (such as videos and images), enabling visual thinkers to compose, remix, annotate, and connect content from their knowledge base and emerging thoughts in a new way.

In addition to its core features, Logseq has a growing ecosystem of plugins and themes that enable a wide range of workflows and customization options. Mobile apps are also available, providing access to most of the features of the desktop application. Whether you're a student, a professional, or anyone who values a clear and organized approach to managing your ideas and notes, Logseq is an excellent choice for anyone looking to improve their productivity and streamline their workflow.

founded 2 years ago
MODERATORS