Allow developers to externalize Mongo queries in javascript files [DATAMONGO-314]

[spring-projects-issues]

Donny A. Wijaya opened DATAMONGO-314 and commented

It would be nice to see Spring Data Mongo to have this feature. Externalizing queries in a separate file will make development cleaner and modular

---

Affects: 1.0 M5

[spring-projects-issues]

Donny A. Wijaya commented

I imagine something like this:

In Java:

@Query(file="classpath:/com/mycompany/userQueries.js")
List<User> findUserByUsername(String username);

In JavaScript (userQueries.js):

function findUserByUsername(username) {
    return db.users.find({'username' : username})
}

[spring-projects-issues]

Oliver Drotbohm commented

We currently support the option to create a properties file classpath:META-INF/mongo-named-queries.properties that can contain query declarations using the ${domainClassName} .${queryMethodName} name pattern like this:

interface PersonRepository extends Repository<Person, Long> {
  List<Person> findByFirstname(String firstname);
}

Person.findByFirstname={'firstname' : 0?}

This approach is supported through all modules implementing the repository abstraction (JPA, MongoDB, Neo4j). Does this suit your needs? It seems your suggestion targets more complex examples but I think a filey-per-query approach will get out of hands quickly and for more complex examples (doing more than just parameter binding and query execution) you're better off with a custom implementation anyway. What do you think?

[spring-projects-issues]

Donny A. Wijaya commented

Hi Oliver,

Sorry, I just noticed your message for this issue. I think the approach you suggested is more than enough. But is it possible to pass an object?

For example,

Java:

List<Person> findByDetails(Details details)

Properties:

Person.findByDetails={'fullName' : {details.name}, 'location' : {details.location}}

Thanks,

Donny