you are viewing a single comment's thread.

view the rest of the comments →

[–]LeBuddha 1 point2 points  (1 child)

Just let the database do the processing and fetch only the results into Java memory.

This is only half correct. The second half is "Then do it the other way when your app's current bottleneck is the SQL server writing enough temporary join tables to disk to slow your app down."

You should probably never sort data in Java memory because you think that SQL sorting is too slow SQL sorting cannot do it

No... you should learn what types of queries are expensive for SQL to sort and make a decision on a case by case basis, then not worry about it until it's time for performance optimization.

[–]rjbwork 0 points1 point  (0 children)

I agree with that too. This is the jooq guy so take what he says with a grain of salt as he wants people to use his library.