You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the decision to implement Neorg GTD against a flexible, associative tag metadata layer, the proposition to cache structures like tasks and links through SQLite tables is off the table.
With SurrealDB now at 1.0.0, support for indexing, and its much stronger support for (property-full) edges, while using Rust, it is now the default.
First priority of implementation is meeting the feature set for Neorg GTD. That means caching and updating:
Task locations in documents
Inline blocks locations in documents
Inline block namespace structures (encoding semantics and ontology of Neorg GTD)
Pre-build query support
Questions:
do we want full-text search support on task bodies etc, or do we jsut return everything and (fuzzy)-match on that separately?
How do we implement the edges between records precisely to model generically, but specific enough?
The text was updated successfully, but these errors were encountered:
With the decision to implement Neorg GTD against a flexible, associative tag metadata layer, the proposition to cache structures like tasks and links through SQLite tables is off the table.
With SurrealDB now at 1.0.0, support for indexing, and its much stronger support for (property-full) edges, while using Rust, it is now the default.
First priority of implementation is meeting the feature set for Neorg GTD. That means caching and updating:
Questions:
The text was updated successfully, but these errors were encountered: