Repository findOne method throws Exception with Oracle [DATAJPA-13] about spring-data-jpa HOT 5 CLOSED

Oliver Drotbohm commented

Fixed with d108bc9

from spring-data-jpa.

Oliver Drotbohm commented

I implemented the fix for a Specification not returning any object. This will result in null being returned now. However I haven't changed the code to implement an arbitrary result in case of multiple objects being returned as we don't have no control over the ordering in that case so that multiple calls to the same data store could result in differing results.

Would it suit you simply calling findAll(Specification spec) and use the first one returned?

from spring-data-jpa.

Oruganti Shanker commented

Yes, what you propose is the best solution. There will be a difference in the findOne behavior when using MongoDB vs Oracle, but we can't avoid a few such differences (;-))

from spring-data-jpa.

Oliver Drotbohm commented

Well I think we could restrict the MongoDB version of findOne(…) to align to that convention. So we would stay consistent and could outline the way I proposed in the comment above in the documentation as a workaround

from spring-data-jpa.

Oruganti Shanker commented

I would say we leave things the way they are now. The Mongo users of the API would expect findOne to return one object, as the Mongo API does. So the best way is to have findOne return what the Mongo API returns.

from spring-data-jpa.