ekZepp@lemmy.world to linuxmemes@lemmy.worldEnglish · 3 months agoTastes like enshittification.lemmy.worldimagemessage-square37linkfedilinkarrow-up1975
arrow-up1975imageTastes like enshittification.lemmy.worldekZepp@lemmy.world to linuxmemes@lemmy.worldEnglish · 3 months agomessage-square37linkfedilink
minus-squareonlinepersona@programming.devlinkfedilinkarrow-up3·3 months agoWhat are you talking about? Logseq uses markdown. The database is built from the markdown files. You can regenerate it at any time.
minus-squaredudleyflippendoodle@lemmy.ziplinkfedilinkarrow-up2·3 months agoYou’re right, you can use logseq without a db. Nice! There is a version that uses SQLite which is what I was using, it seems like that’s required for certain features like db graphs, so a bit of a bummer: https://github.com/logseq/logseq?tab=readme-ov-file#-database-version
minus-squaredudleyflippendoodle@lemmy.ziplinkfedilinkarrow-up1·3 months agoperformance isn’t really my main concern with DB.
What are you talking about? Logseq uses markdown. The database is built from the markdown files. You can regenerate it at any time.
You’re right, you can use logseq without a db. Nice!
There is a version that uses SQLite which is what I was using, it seems like that’s required for certain features like db graphs, so a bit of a bummer:
https://github.com/logseq/logseq?tab=readme-ov-file#-database-version
deleted by creator
performance isn’t really my main concern with DB.