• Stumblinbear@pawb.social
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    1 year ago

    Unfortunately RustRover is still garbage for actual usage. And I refuse to use an ORM when I can just write the SQL in a more common syntax that everyone understands across every language instead of whatever inefficient library-of-the-week there is. Raw SQL is fine and can be significantly more performant. Don’t be scared.

    • hikaru755@feddit.de
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      I’m not talking full blown ORM here, not a fan of those either. I’m talking about some light weight wrapper that basically just assembles SQL statements for you, while giving you just a little more type safety and automatic protection against SQL injection, and not sacrificing any performance. I’m coming from the JVM world, where Jooq and Exposed are examples of that kind of thing.

      • Stumblinbear@pawb.social
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        I’m currently using SQLx which you write raw queries in and it validates them against a currently-running db, using the description of the tables to build the typing for the return type instead of relying on the user. It makes it pretty hard to write anything that supports injection

        • hikaru755@feddit.de
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Oh, that sounds really cool! At what time does this validation happen? While you code, or later at build time?

          • Stumblinbear@pawb.social
            link
            fedilink
            arrow-up
            3
            ·
            1 year ago

            Happens at compile time! It’s relatively quick. You can also run a command to write the query results to file for offline type checking which is mostly useful for CI