Skip to content

Commit

Permalink
bump date
Browse files Browse the repository at this point in the history
  • Loading branch information
logseq-cldwalker committed Oct 16, 2024
1 parent bad24f9 commit e45a600
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions db-version.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
## Description

This page describes DB (database) graph functionality as of Oct 1st. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
This page describes DB (database) graph functionality as of Oct 15th. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).

NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we recommend only using this for testing purposes.

Expand Down Expand Up @@ -308,4 +308,4 @@ An automated backup of graphs is available by clicking on the upper right three

Currently the graph can only be exported as a [SQLite](https://sqlite.org/) DB file. To do so, click on the three dots menu in the upper right corner, select `Export Graph` and click the `Export SQLite DB` item. This creates a .sqlite file for use with Logseq. From that same menu, you can also select `Export both SQLite DB and assets` to create a .zip file which contains the .sqlite file and any asset files packaged as a .zip file.

To import the exported .sqlite file, click on the three dots menu in the upper right corner, select `Import` and click the `SQLite` item.
To import the exported .sqlite file, click on the three dots menu in the upper right corner, select `Import` and click the `SQLite` item.

0 comments on commit e45a600

Please sign in to comment.