Working in db-Version

Hello outthere,

I try to prepare myself and my graph for the database version.
I have a few questions and would appreciate all kinds of experiences or inspirations how you do it atm.
I have tried importing my graph into test.logseq.com. But I wonder where the uploaded data is stored? I don’t see any changes in the folder that I uploaded and can’t find a hint where to search for it.

Also I wonder how my workflow should change and how to change the graph I currently use. I read db-version.md and db-version-changes.md but don’t really get a starting point.
Will I have to change all my inline tags with [[]] ?
And I don’t really get the nodes-thing. What is the point of nodes now? And How do they interact with pages and blocks?

Also, does one of you also work with the ‘real’ database version by cloning db-branch from github and building it yourself?

greetings and thanks for your time

Spelloverflow

5 Likes

Hi there,

From what I understand:

  1. You data is currently only saved in the browser cache. You can export your data as SQLite DB and save this somewhere - currently this is the only “physical” way of seeing your data. Once the devs release a desktop app, I am sure you will be able to select where to store the SQLite file.
  2. In terms of workflow, mainly facilitates the use of creating databases through properties so you can see data in different views and whatnot, a la Notion. There is a considerable amount of discussion on the Tags vs [] but I am not sure how the devs concluded this.
  3. There are a few people from the Discord that have got the DB version up and running from the GH branch, but it sounded like such a headache that one user commented “just wait for the devs to cut a desktop app” - or something similar.
  4. I took as nodes to mean something like, you have an author Tag and in it you specify a name. In the book Tag, you have a property called Author based on the Author node (i.e. the author is someone you have marked up as Author).

Hope this helps

4 Likes