fiatjaf on nostr

@unclebobmartin 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?

fiatjaf @fiatjaf · 42w

SQL was never intended to be used by computer programs. It was a console language for printing reports. Embedding it into programs was one of the gravest errors of our industry.

4❤️3❤️1

fiatjaf · 42w

Or is it because SQL is associated with servers running externally to the programs that use the data and as such they constitute a weird unnecessary slow abstraction that isn't needed for 99% of the programs we write today that could pretty much use an embedded simpler database or sometimes just som...

Nadia · 42w

Also interested in the answers to these questions nostr:npub19mun7qwdyjf7qs3456u8kyxncjn5u2n7klpu4utgy68k4aenzj6synjnft

unclebobmartin · 42w

Precisely. It is utterly insane for programmers to communicate with a database by constructing strings in an arcane language that is then compiled in real time. Not only does this open a whole bunch of bizarre, security holes, it’s just plain dumb. We are programmers, we communicate with our libr...

Brunswick · 42w

Dynamically compiling SQL query strings in our programs is something so stupid even southpark couldn't sufficiently mock it