I wish writing SQL queries was more popular than ORMs

@Lmaydev@programming.dev

The SQL generation is great. It means you can quickly get up and running. If the orm is well designed it should perform well for the majority of queries.

The other massive bonus is the object mapping. This can be an absolute pain in the ass. Especially between datasets and classes.

Cyclohexane

I find SQL to be easy enough to write without needing generation. It is very well documented, and it is very declarative and English-like. More than any ORM, imo.

@Lmaydev@programming.dev

I don’t c#'s EF is brilliant

dbContext.Products.Where(p => p.Price &lt; 50).GroupBy(p => p.Category.Id).ToArray()

@immutabletest@lemmy.world

LINQ looks great with the query syntax:

var productsByCategory =
    from p in dbContext.Products
    where p.Price &lt; 50
    group by p.Category.Id
    select p;

JWBananas

  p.*
FROM
  Products p
WHERE
  p.Price &lt; 50
GROUP BY
  p.Category_Id```

Meanwhile the ORM is probably generating something stupid and unnecessarily slow like this:

```SELECT
  p.*, c.*
FROM
  Products p
JOIN
  Category c
  USING (Category_Id)
WHERE
  p.Price &lt; 50
GROUP BY
  c.Category_Id```

Now stop using goddamn capital letters in your table and field names. And get off my lawn!

@Lmaydev@programming.dev

No it creates the first one. You can actually use a .Select to grab only the fields you want as well.

If I added .Include(p => p.Category) it would also populate the Category property. At the point it would have to do the join.

Also the table and field names can be specified via attributes or the fluent model builder. Those are the C# object and property names.

I wish writing SQL queries was more popular than ORMs

I wish writing SQL queries was more popular than ORMs

Programming

Rules

Wormhole