Quantcast
Channel: Why the database version and how it's going?
Browsing latest articles
Browse All 25 View Live

Why the database version and how it's going?

if there will be no “native” writing to the markdown files as a back-end of Logseq data I suppose that exporting/importing will be the only way to get into markdown the contents of the database or to...

View Article


Why the database version and how it's going?

We plan to experiment with two-way sync (either real-time or periodically) between the db and markdown files once the db is more stable. Read full topic

View Article


Why the database version and how it's going?

I want to know if I can find a specific text and replacement in DB version . Now I finish it by editing the md file of logseq through VScode. Read full topic

View Article

Why the database version and how it's going?

Thank you for the insightful update. It is impressive to see the remarkable progress made so far, and I eagerly anticipate the release of the DB version. Best of luck! Read full topic

View Article

Image may be NSFW.
Clik here to view.

Why the database version and how it's going?

tienson: To facilitate advanced querying, the new database version should offer support for Datalog queries. Very nice! tienson: No, we’ll continue to support both file-based and database-based...

View Article


Image may be NSFW.
Clik here to view.

Why the database version and how it's going?

zizhuo: I want to know if I can find a specific text and replacement in DB version In SQL-supporting databases it is possible to use some external client to execute a statement looking like this:...

View Article

Why the database version and how it's going?

Find and replace will be built-in. Read full topic

View Article

Why the database version and how it's going?

Afaik the DB version is much more stable than the current version because we’ve been focusing on avoiding any issue that can result in data invalidation, we’ll also try our best to reduce any issues...

View Article


Why the database version and how it's going?

Thanks for the suggestion! This doesn’t work for the db version because the graph data is stored as key-value pairs (id->serialized node in a tree) in a table, the safe way to update contents might...

View Article


Why the database version and how it's going?

I think that @zizhuo’s question was twofold: Whether the database version will support replacing. Which got a positive answer. No good reason for not supporting it. Actually Logseq could implement...

View Article

Why the database version and how it's going?

with the current implementation, if I modify a template or a custom command I can’t have all templates in the markdown-based “db” updated accordingly (if even for an additional property I inserted in...

View Article

Image may be NSFW.
Clik here to view.

Why the database version and how it's going?

tienson: We’ll also extend invitations to a select group of users and companies to test our real-time collaboration feature once it’s ready for feedback. Curious about who will be qualified or how you...

View Article

Why the database version and how it's going?

Thanks for the question, we’ll start with our active contributors and sponsors. Read full topic

View Article


Why the database version and how it's going?

Thanks for your quick reply! I have no idea that whether i can be catorized as “actve contributors” (2 PRs, 1 merged and 1 WIP) or not, But as a heavy user of logseq, I really want to participate in...

View Article

Image may be NSFW.
Clik here to view.

Why the database version and how it's going?

Thank you for your contributions! Can you send me a direct message with your email address? I’ll add you to the testers when it’s ready. Read full topic

View Article


Why the database version and how it's going?

I’m also very excited for the DB version as the improved stability will be very welcome. But as referenced in another comment, I’m a bit worried about lock-in. Will the new database be open source and...

View Article

Image may be NSFW.
Clik here to view.

Why the database version and how it's going?

tienson: Are you going to deprecate Markdown files support? No, we’ll continue to support both file-based and database-based graphs, with a long-term goal of achieving seamless two-way sync between...

View Article


Why the database version and how it's going?

+1 for the same question on orgmode Read full topic

View Article

Why the database version and how it's going?

Great job! This is exciting stuff. Can’t wait to get my hands on and play with it. Read full topic

View Article

Why the database version and how it's going?

@tienson and the entire team. Thanks for the hard work in the new DB version and thanks also for engaging with the community with this post. Highly appreciated Read full topic

View Article

Why the database version and how it's going?

All great questions, thanks! I’m a bit worried about lock-in. Will the new database be open source and allow for SQL queries? What’s the reason Logseq couldn’t go with a solution like SQLite? Our...

View Article


Image may be NSFW.
Clik here to view.

Why the database version and how it's going?

Jordan_Garrison: will this also be true for org file support? @leod TBH we’ll not support org files in the beginning because we don’t have the resources to support both Markdown and Org Mode, our goal...

View Article


Why the database version and how it's going?

Going to sleep soon, I’ll catch up tomorrow! Thank you everyone! Read full topic

View Article

Why the database version and how it's going?

This is very exciting. I hope that the multi-window mode will be more reliable with the DB version. Read full topic

View Article

Why the database version and how it's going?

A post was split to a new topic: Questions about the upcoming database version Read full topic

View Article

Browsing latest articles
Browse All 25 View Live