3 ms·
I don't think you can really call something a database if it doesn't have a query language, at least in contemporary practice. And I wouldn't call "cd", "ls",
by crazygringo 4y ago
I don't think you can really call something a database if it doesn't have a query language, at least in contemporary practice.
And I wouldn't call "cd", "ls", "mkdir", "rm", "cat" and "echo" a query language.
Even the first navigational databases had a proper query language, although radically different from SQL.
- gkbrk 4y agoWould you call "get", "set", "del" and "rename" a query language? Because they are commonly used commands for Redis.
- ta988 4y agoNow add find, grep, xargs, sed, awk and put all those together with pipes
- jabbany 4y agoConsidering things like wildcards and glob matching these don't seem far off from what you'd use in a graph db query language. (E.g. something like neo4j)
- esjeon 4y ago"Language" is just an interface. You can SQL a filesystem if you want, and also can build 3rd party indexers that query engines can benefit from.
- hasperdi 4y agoExactly! https://osquery.io https://osquery.io is one example that
- kevin_thibedeau 4y agoPath syntax with shell globbing is the query language.
- tadfisher 4y agoThere are plenty of databases without associated query languages. RocksDB, FoundationDB, and LMDB to name three. "Queries" are generally "list keys in this range" and all of the higher-level metadata you would want to query on (e.g. relations) are encoded in the key. I would absolutely put filesystems in this camp.