I see that there are three similar plugins. Do you know what the differences between them?
My other questions:
Developers get so wrapped up in their own development excitement that they forget to introduce their purpose and application scenarios.
I’ll just paste this here in case it’s useful to anyone feature comparison new database plugins - Google Sheets
In short, database folder plugin works more like the kanban plugin, it takes the full pane, but database plugin is more like dataview, where you can create multiple code blocks in one note.
the db folder plugin is also a markdown note, which you can see the code block of it. Why is it can’t be used multiply in one note?
It creates a custom view to display the database.
I’ve been using the DB folder plugin and I can say that it has a very clear roadmap of what it wants to implement versus not. Also another reason why I support him over the database plugin - I like responsive developers who share their vision of what the end-product may look like.
Roadmap:
Also, I do enjoy this concept of choosing an entire folder as the database. By combining it with other plugins such as Auto Note Mover, you can create some really creative and convenient workflows.
Not to mention if you don’t like using an entire folder as the source, he has recently released using tags as sources.
Also, he’s also released recently the ability to use entire dataview queries as sources - meaning that you can convert your dataview query into an editable database table.
Some exciting things he has planned for the long-term include Notion Formulas, Relational databases, Mobile support and more.
what is the strengths and weaknesses of custom view over rendering code block in view mode?
Also, what does the slash in the comparison sheet mean?
The custom view have more space but can only have one db per pane, the code block can have multiple db per pane but have less space. Just to note that folder db plugin is planning to support multiple views, so this drawback will be somewhat reduced.
The slash means that the plugin was not meant to provide such a feature.
Wow, this comparison is super useful!
I really like the DB folder plugin, it’s like using dataview for tables but with multi-column sorting, filtering and search.
The UI is a little sloppy though, it took a fair bit of polish to make it look better…
Any chance you could share the CSS fixes you applied and/or share it with the author of the plugin through an issue/PR on Github? Looks slick! Good job 
Mind to share your customizations? The rough UI really makes me not want to make use of folders db.
I realize the comparison likely isn’t actively kept up to date but I’d like to share that projects can indeed use tags as a data source.
If you want, I can give you access to modify it. Do you want to ?
Edit: I’m updating it now to match the changes, thank you.
Thanks for this comparison sheet.
The Metadata Menu plugin comparison will be great in this list.
And there is going to be a new core database plugin, currently called Databases.
It’s not meant to be used as a database plugin, more like advanced property management, and it doesn’t provide a table view, that’s why I didn’t include it in the list.
Great catch, I included it in the list and as soon as it becomes public, I’ll tick the corresponding checkboxes.
I have tried it and its same like a database thing - does provide table view as well for each class.
One of the videos showing its functionality
Yeah, I saw that video at some point and I noticed that it’s specifically designed for file classes, not regular files. It’s a bit tricky to set up and test, so I prefer not to include it in the comparison.
