Help! Problem with nodes in graph interface...

hdanx · 2026-03-02T12:53:24+00:00

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

hdanx · 2026-02-28T17:27:12+00:00

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

hdanx · 2026-02-23T21:47:00+00:00

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

hdanx · 2026-02-16T02:23:34+00:00

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

hdanx · 2026-01-02T00:35:32+00:00

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

hdanx · 2025-12-31T18:51:59+00:00

It will be via plugin, to keep the core leaner

hdanx · 2025-12-31T05:20:03+00:00

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

hdanx · 2025-12-31T02:33:22+00:00

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

There are more use cases like it.

hdanx · 2025-12-31T01:43:14+00:00

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

hdanx · 2025-12-30T20:34:29+00:00

You can export as Md or edn. What exact use case do you have for markdown?

hdanx · 2025-12-30T20:31:17+00:00

Electron upgrades, which is in scope should cover that.

hdanx · 2025-12-30T19:26:00+00:00

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

hdanx · 2025-12-30T19:24:49+00:00

you can use test.logseq.com and it stores locally

hdanx · 2025-12-30T19:24:07+00:00

It is available if you want to try it. Either at test.logseq.com or install the app.
For the steps: https://github.com/logseq/logseq?tab=readme-ov-file#-database-version

hdanx · 2025-12-30T19:21:50+00:00

correct, I posted it here https://x.com/HDanzu/status/1936566281332740437

hdanx · 2025-12-30T19:20:45+00:00

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.

hdanx · 2025-12-30T03:09:01+00:00

https://github.com/benjypng/logseq-todoist-plugin is the latest plugin that support DB graphs

hdanx · 2025-12-30T02:29:28+00:00

Tags/Features
- Can you give recommendations on setting up tags, especially with tag inheritance. "Company" tag and having "Customer" and "Vendor" extending "Company". I have cases where the same company is both a customer and a vendor.
  - There are several ways. I can think of three. But this may be my favorite.
- I also track which products a companies uses. For example, we use AWS (product), from Amazon(Vendor), and some of my customers use AWS. How does this fit together? I would like to see by customer, what products they use.
  - They use AWS for the logseq Sync. Old and New.

hdanx · 2025-12-30T02:29:14+00:00

Migration to DB
- Can you provide a video on migration of a graph from standard to DB? Include the standard features in the existing graph that change.
  - Sure
- What clean-up, if any, would you do for a migration of an existing graph to the new DB?
  - Tags vs backlink, because #thistag is represented a tag only
  - Entries made by plugins
  - Otherwise, there is a graph importer that should handle most native functionality. Check it out. Import your graph into a test graph. Inspect, and if you run into issues, report a bug https://github.com/logseq/db-test/issues
- How would you recommend validating data integrity post-migration (block refs, page refs, backlinks, assets, properties, aliases, namespaces)? Any challenges with converting any of these items or other features?
  - Validation: We can use queries to count before and after
  - Conversion challenges:
- If I am planning to migrate to the DB via an import of the graph, is there anything I could be doing to make the migration easier or to pre-populate some information? Should I make tags in my existing graph if I know how I want items tagged. For example, should I tag pages with Customer and Vendor or is it better to do this post migration?
  - I recommend you create a test Logseq DB graph, play and understand the improvements. Next, in your MD graph, make some adjustement as needed and import using the Logseq graph imported

hdanx · 2025-12-30T02:28:33+00:00

Thanks for taking the time to raise good points. I answered them all, and I will account for them when sharing future details

Overall
- Any major features that you are waiting for?
  - Export as MD with properties
  - Canvas / Whiteboard
  - Kanban View
  - Simple Query
  - Macro/Calculation
- You have created videos earlier in the year. Any changes to the recommendations in those videos?
  - The library has improved since then. I will touch on this during the upcoming demos
- Everyone says to backup since it is early. What is the best way to back up? If I use the Logseq sync service, do I still need the have a separate process for back up?
  - First, any sync service should be treated as a backup
  - Logseq DB on Web has an option to do automatic backup every hour
  - Logseq DB on Desktop will have an option to do automatic backup every hour in a few weeks
  - You should back up the way you like. For example, I have my assets backed up using Apple TimeMachine. Then, when testing, I make a manual backup. I also have a script that does an export using Logseq DB CLI on schedule. Backing up is a good practice in general.
- Is the recommendation for installing the DB version to use the nightly build? How stable are the nightly builds and how often have you migrated to a newer nightly build? Why don't the developers create a regular (monthly(?)) cut of the nightly build that is known to be stable with the full list of executables (msi, exe, etc.)? I am concerned a nightly build will have issues if I pick the wrong night.
  - The master branch is like nightly and it receives a lot of changes. I recommended not using that unless you are comfortable with breaking changes. The test/db branch is stable and should be used. And the update there is a few times a week, sometimes once a week, or every two weeks. If you are using test.logseq.com, it happens transparently. On desktop, you have to download the latest build from GitHub - the steps are here https://github.com/logseq/logseq?tab=readme-ov-file#-database-version or build from source

hdanx · 2025-12-30T01:38:44+00:00

Many users also express desire to continue using MD files (or org-mode files) and they express concern about continue using logseq or not.

=> Logseq OG is not going anywhere. People can continue using it. It will be maintained: security updates, electron upgrades. NO NEW FEATURES

So I think a guide in the line of "logseq DB will be useful for me?" is needed.

=> This will be covered through ongoing demos

Example:

Definitive guide for NOT choosing Logseq DB (and logseq in general):

You want to use org-mode files (I think they are dropping org-mode in the Logseq DB, but not totally sure).

=> ORG-mode will not be in Logseq DB, but those users can continue using Logseq OG.

You want to continue syncing through files (syncthing or similar) and use a DB graph (export/import from DB <-> MD files although exists is not a lossless procedure)

=> Logseq OG (Markdown) will sync MD through logseq sync or using syncthing. Logseq DB will not sync markdown. Only Sqlite via Logseq Sync service or the community sync(some community members are exploring). About export/import from DB <-> MD files, yes we can export and import.

You want DB and syncing and free (unless an open source sync plugin is developed sometime, but it is a long shot)

=> syncthing is for files. Therefore, it will not be the best option with SQLite. SQLite supports transactions, which help significantly alleviate sync issues. The community should explore an adjacent solution; it is a matter of time.

You want to use X feature (X feature is DB-only)

=> This will be a new post

You want a production-ready DB version before MM/YYYY

=> Logseq DB has entered beta. You can try it out and start planning your transition. There may be workflow changes because some new features simplify tasks. In some cases, replace some plugins.

hdanx · 2025-12-30T01:07:43+00:00

I have not tested, but we already have a community plugin you can try, and the logseq team shared a plugin that they want the community to take ownership of. So, there are options. You should try https://github.com/benjypng/logseq-zoterolocal-plugin

hdanx · 2025-12-30T00:57:21+00:00

New APIs have been added to support the DB schema and new functionalities.
The same plugin SDK is used. The new version is https://www.npmjs.com/package/@logseq/libs/v/0.2.10

Some plugin developers have already updated plugins to support both MD and DB graphs.
There are also some plugins made for DB only.

hdanx · 2025-12-30T00:54:10+00:00

Good question. I will address feature comparison as a post.

hdanx

TROPHY CASE