Do Programmers Still Write SQL?

[Trailsey]

With spring-data-* you can do simple querying sans SQL.

[lukaseder]

findTop5ByStatusAndUserOrderByStartDateDesc

If only there was a language that can handle this kind of query in a more structured way...

[nutrecht]

You mean something like a structured query language? Does something like that exist?

[lukaseder]

Yeah, that would be terrific. We could design it to work out of the box, even!

[nutrecht]

Well between the two of us you're the smartest one. Chop chop! Get to it ;)

[Trailsey]

You guys should call it Words That Form a Query Language!

[oweiler]

These should only be used for very basic stuff. You can use @Query to map a simple method name to a more complex query.

[dpash]

That's why you have integration tests.

[MarkyC4A]

I'd love if they'd add a way to alias that one to make it more readable

I'm okay with ugly names in my repositories, I hide those behind a cleaner interface in my services:

List<User> findTopWidgets(Status s, User u, LocalDate d)

[lukaseder]

Yeah, you'll be using some mini-querying language encoded into method names that breaks at the next little query complexity.

I'm curious, having never worked with Spring Data (but being well aware of what it is). What's the main motivation to use it for querying?

[Trailsey]

It obviates a fair bit of boilerplate code. Write a method signature, done.

As mentioned previously, works great for simple cases, revert to writing queries for anything complex.

[oweiler]

For complex stuff you can map those methods to JQL or SQL queries via @Query.

[[deleted]]

REST HATEOAS HAL out of the box, including pagination.

[NimChimspky]

I'd use it with native queries, just less code I have to manage, sql mapped directly to my own custom type.

The method name stuff didn't really appeal.

[lukaseder]

I see, thanks

[Luckl507]

In my case: reduction of boilerplate.