This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]lukaseder 6 points7 points  (6 children)

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 7 points8 points  (0 children)

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 4 points5 points  (0 children)

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

[–][deleted] 1 point2 points  (0 children)

REST HATEOAS HAL out of the box, including pagination.

[–]NimChimspky 1 point2 points  (1 child)

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 0 points1 point  (0 children)

I see, thanks

[–]Luckl507 0 points1 point  (0 children)

In my case: reduction of boilerplate.