3 ms·

"I feel like this is the sweet spot―give me a thin abstraction over SQL and do the gruntwork of converting domain entities to tables and vice-versa, but nothing

by ak39 8y ago

"I feel like this is the sweet spot―give me a thin abstraction over SQL and do the gruntwork of converting domain entities to tables and vice-versa, but nothing else, thanks." Something like iBatis/nBatis? (Haven't used this since 2004)

lukaseder 8y ago
jOOQ!
- coleifer 8y ago
  jOOQ is legit. I found it very helpful to read jOOQ as I was writing my own library in python. There's a huge difference between a query-builder and something like hibernate or sqlalchemy. Query-builders make it easy to compose queries, leaning on your programming language to enforce syntactic correctness. When you're dealing with SQL directly, composition means string concatenation. A query builder gives you a data-structure that represents a query. I think it's helpful to distinguish between query-building and object mapping when the "orm-vs-sql" thing comes up.
  - lukaseder 8y ago
    What's your library?
    - coleifer 8y ago
      "peewee" - https://github.com/coleifer/peewee https://github.com/coleifer/peewee
      - lukaseder 8y ago
        Very cool (and how could I miss it?)
michaelcampbell 8y ago
*Batis is still a thing, and is closer to what they were asking for, but you're still mapping your domain to hand-coded SQL. That's not bad, necessarily; I just don't know if his "abstraction over SQL" means you write it and your domain code uses that abstraction, or it's provided by the framework.