Evan Martin (evan) wrote in evan_tech,
Evan Martin
evan
evan_tech

sql

Why do we use SQL? It seems every serious user of SQL has some abstraction layer on top of the language, either DBI-style quoting (select x from y where z=?) or a fancier object layer. I recall that at least for compilation the lexing step takes a significant fraction of the processing time. So why not feed the database some sort of preparsed/binary query, and make this human-friendly text interface just part of a frontend that converts to database-speak? (See also: Graydon's work on an SQL extension for OCaml, which would have made it a compile-time error to generate a malformed query.)
Subscribe

  • livejournal kids

    Neat image from Jack Dorsey. Every so often someone will ask me about Twitter and I'll dig up a a random day from Brad's LJ in 1999 and talk about…

  • ljrb release 0.3.1

    LiveJournal Ruby module update: This release won't die when the "useragent" property is present in an entry. I've also added support for passing…

  • ljrb 0.3.0

    ljrb 0.3.0: This release adds support for the "current_location" field and fetching friendofs in the same request as fetching friends. There's also…

  • Post a new comment

    Error

    default userpic
    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 16 comments

  • livejournal kids

    Neat image from Jack Dorsey. Every so often someone will ask me about Twitter and I'll dig up a a random day from Brad's LJ in 1999 and talk about…

  • ljrb release 0.3.1

    LiveJournal Ruby module update: This release won't die when the "useragent" property is present in an entry. I've also added support for passing…

  • ljrb 0.3.0

    ljrb 0.3.0: This release adds support for the "current_location" field and fetching friendofs in the same request as fetching friends. There's also…