> The first sentence of the documentation already says it: "turn any set of notes into a powerful database

No, horrible job at explaining. What does it mean to turn any set of notes into a powerful database? What does it mean to "turn"? Does it mean that a file will become a database? Or does it mean that a file can be interpreted as a database? And why set of notes? If I have a single note, can I turn that into a database too? Are the records of the database files, or items in a file? What is happening when I type ![[Untitled.base]]? Is the file where I typed that a database now? Or does that text assume that the file named Untitled must be a database?

They do a horrible job at explaining it.

▲

steve_adams_86 3 days ago | parent | next [-]

I'd like a demonstration of what's powerful about it.

Like, why would I want to take advantage of this, and how? I'm with you here. I don't get it. I can stick data into SQLite and do all kinds of neat stuff. Why am I preferring a mushy database trapped inside Obsidian?

	▲	atoav 3 days ago \| parent \| next [-]
		Well everything comes in shades. Lets say you write meetingnprotocols of your meetings down with obsidian. The markdown/freeform and cross-linkable text body of obsidian is perfect for this. But you'd now be able to have a bit richer search over the notes based on who was present. This allows relatively normal people to do that, without having to dive too deep into databases plus it already lives in the app where you take the notes. As someone who uses Sqlite for a ton of things I don't think the exietence of sqlite makes this useless.
	▲	theshackleford 3 days ago \| parent \| prev [-]
		This is obviously for people for whom notes are a primary knowledge storage mechanism, and for whom that mechanism is obsidian. I “could” stick data in SQLite but if I’m not then it’s quite useless to me.

▲

slightwinder 3 days ago | parent | prev [-]

> What does it mean to turn any set of notes into a powerful database?

You must be fun at parties. Complaining about everything, but not even bother to read the damn manual... It's explained on the third sentence on that site. Ok, to be fair, there is a big picture between those parts, and you have to follow some links for more details.

> And why set of notes?

Just curious, do you even know Obsidian? Have you ever used it? You read like someone who has no clue about this software, jump right in the middle of the manual, and then complain that you missed the tutorial.

Obsidian is a markdown-editor with knowledge base. Notes are its lifeline, and they have since nearly the beginning the option to put metadata into each note in a special section (in yaml), basically the header of the note. This metadata are now called properties. Bases is a feature building up on this metadata, offering a database-like experience for viewing and editing them in a specialized UI. The database, is the vault, the folder+subfolder containing the notes. Each note is a row in that database.

This is all explained in the documentation, if you just would read it...