IMHO just like machine learning is statistics on steroids, I would not be surprised to see some neural networks and embeddings try to model statistics for RDBMS in the future.
These models could just as well be these that can be used to infer if a user row is bound to add another order row, and which kind of product row to go with that.
I'm also a fan of using CTEs in a template, so all template arguments can be grouped together at the top of the query.
Additionally, multiple CTEs in a query execute as a single transaction, and in order (well, for Postgres anyway and probably SQL server) which can allow for multiple (different dependent tables) updates in a query without the roundtrips to say the API layer.
This isn't a linq vs SQL debate. I'm pointing out that linq allows explicit ordering, and if you know the shape of your data, you can account for changes in it.
As with most coding, right tool for the job, YMMV for SQL or linq.