I’ve built a really nifty and fairly robust system to two-way sync logseq tasks with Apple iOS Reminders via Shortcuts and iCloud (my logseq drive is hosted in icloud for this purpose). Will we be able to ask Logseq to use the database for 90% of content, but mark a few topics / files as MD only so automations like my system can continue to work?
PS happy to share my Shortcuts setup if there is interest … it took a while to get working robustly!
Will the DB version mean it’s more likely we might also get the option for true WYSIWYG editing experience?
fyi i built a shortcut with reminders sync using the Logseq API, could (?) work with the DB version. Here: GitHub - flegfleg/logseq-reminders-sync: Shortcuts to sync tasks (with deadlines) between Logseq and Apple Reminders
It syncs task name, due date, status to reminders, and then task status (TODO, DONE) back to Logseq (omitting any changes to name and due date), but it could be reworked for a complete sync.
Looks like the web version will be powerful. Super excited to get my hands on it.
Will we be able to self-host it? I mean will we be able to host that sqlite database on the server alongwith the app? (to ensure smooth sync for free users?)
And will we still have git sync?
That’s an absolute important question- for me, having .md files is one major requirement, I don‘t want/ need a DB version, is it still being maintained?
Currently a query result is just a static output of the relevant content.
With the db version, will it be possible to edit the actual values, directly within a query result in table view?
For example, say I have hundreds of blocks representing books, each with a property for author. Then I do a live query showing all these books in a table, including a column for author. Then I would be able to change the authors names directly in that table (as in a spreadsheet software).
How will version control (git) work with the DB version? I rely on git for incremental backup and tracking changes. This is trivially easy to do when working with clear text / markdown.
You already can if you know how to do it, the branch on GitHub is feat/db.
I want to know if the page in the database version can be easily converted into PDF for sharing、printing. The export effect of the current plug -in is average and there is a linked jump failure.
When Logseq implements database as a way of storing the data, does that mean that file will no longer be in plaintext? I’m asking this mostly for GIt syncing.
Will there be a truly Portable version along the other installers? We need not install Logseq on all the devices we touch for privacy reasons. Also I don’t want any data to be left on a device where I start Logseq to note down journal entries along PKM and Task Management entries …
I never worked with databases except doing simple queries, and was wondering how is data stored in a file system? I guess it’s not one file representing one page. Where can I learn more about this, i.e. database and how is data stored on a filesystem.
SQLite uses a single file while PostgreSQL for example multiple files. I think Logseq will just use a single file.
Hi,
Do you think the database version will facilitate the migration from Roam Research?
I am asking because the migration process is taking me much more effort than I originally thought. This is due to two main issues:
I have the intuition that the database version could directly solve the first issue and maybe help with the second one. But if not, I’m interesting to know to avoid waiting in vain 
Since many people seems to also consider migrating, this could be useful information in general.
Thank you
When are we getting the replies for these?
I won’t be replying to the questions directly; the questions are input for a blog post I’m writing. You can find the outline of the questions I’ll tackle first in the OP of this thread.