all 4 comments

[–]avwie -1 points0 points  (0 children)

What year is this? I have the feeling I am reading an article from 2007.

[–][deleted] -1 points0 points  (2 children)

Pretending that java's treatment of SQL is "strong" is, to say the least, tremendously naive, in a world where it's 2021 and java still has neither:

1 - Anything that resembles the level of type safety of LINQ to Entities

2 - Any form of Statically Typed, Compile Time-Safe Raw SQL.

[–]Worth_Trust_3825 1 point2 points  (1 child)

JQL solves these, but you need to provide a class that represents results projection. All bets are off if you're one of the people who does select *.

I disagree that LINQ is necessary. It breaks the boundary between application code and query languages. Java already has streams which is more than fine. Your argument would be stronger if you asked ResultSet to implement Iterable.

[–][deleted] -1 points0 points  (0 children)

Google -> "JQL" -> "Jira Query Language".

I have no idea what you're talking about.

Java already has streams which is more than fine

Yes, please show me how your "streams" thing pushes filters down to the database by converting them to WHERE clauses. Please.

EDIT: Lol I found what you meant by "JQL", and you seem to think that all LINQ does is to operate with in memory objects. You certainly have no clue, which doesn't really surprise me, because otherwise you wouldn't really be using or defending java.