Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Database version #9858

Draft
wants to merge 3,315 commits into
base: master
Choose a base branch
from
Draft

[WIP] Database version #9858

wants to merge 3,315 commits into from

Conversation

tiensonqin
Copy link
Contributor

@tiensonqin tiensonqin commented Jul 14, 2023

This PR adds database backed graphs to Logseq. With a database graph, we will be able to develop richer features more quickly and save fine grained data like block-level timestamps. Database graphs will come with new major features like classes, property types and much more...

Notice: This branch is under development and will go though internal testing, alpha/beta testing before a final release. This means it'll take months before the release.

@djeear-github
Copy link

I want to get into advanced queries. If Logseq gets a new database, is it better to wait with that until that database is in place?

@github-actions github-actions bot requested a deployment to logseq-db-demo (Production) August 23, 2023 05:19 Abandoned
Already useful for testing and will be for more interesting generation
cases
Also fixed a dsl-query sorting bug where nil property values where
incorrectly being treated as greater than non-nil values. Also
fixed a bug where blocks with an explicit :block/created-at weren't
being set for sqlite-build
I think caused by recent macros parsing or whiteboard changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet