-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
tiensonqin
wants to merge
3,315
commits into
master
Choose a base branch
from
feat/db
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
[WIP] Database version #9858
+88,375
−24,782
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
bot
requested a deployment
to
logseq-db-demo (Production)
August 23, 2023 05:19
Abandoned
fixes LOG-3140
fixes LOG-3145
fixes LOG-3136
Already useful for testing and will be for more interesting generation cases
and journal pages
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.