Replying to Avatar fiatjaf

nostr:nprofile1qqsza7flq8xjfylqgg66dwrmzrfuff6w9flt0s72795zdrm27ue3fdgct4s0j is this because you don't think it's wise for a weird Cobol-like string of instructions -- that first have to be generated by the host (with all the care to prevent malicious injections and all the refinement of string concatenation otherwise) and then parsed by the database -- to act as the API between two programs because they could pretty exchange structured data instead?

nostr:nevent1qvzqqqpxfgpzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqyd8wumn8ghj7mr0vd4kymmc9enxjct5dfskvtnrdakj7qg6waehxw309ac8junpd45kgtnxd9shg6npvchxxmmd9uq3kamnwvaz7tmjv4kxz7fwwajhxar9wfhxyarr9e3k7mf0qqsxz55wldnzvvwsudlgrusqwpwxcar8x9625zmrgvpykhe9fwn4jdg5tvfqt

Or perhaps it's because the whole "relational" stuff hides the nasty parts of arranging, indexing and querying data from the programmer and creates a vicious cycle of dependence and incapability that makes the average programmer think anything an SQL query can do is at the same time "magic" (because no one knows how it's done) and "natural" (because everybody can do it since it's assumed everybody is using Postgres or MySQL).

You can see an example of that in any of the many discussions about what features the Nostr "query language" should support.

Reply to this note

Please Login to reply.

Discussion

No replies yet.