Closed alapierre closed 2 months ago
I checked this in micronaut-data 4.1.4 where it worked without errors (the error begins with 4.2.0).
However, even then the query that was being executed was not correct. This is what was being executed SELECT operationLog_ FROM com.example.OperationLog AS operationLog_ WHERE (operationLog_.id = :p1)
and because the field is UUID it was returning correct value as being unique.
However, I think the correct way would be to remove this custom method Optional<OperationLog> findById(UUID id, String tenant);
and use default one Optional<OperationLog> findById(UUIDTenantId id)
.
Good point Radovan, thank you. Using default repository method Optional<OperationLog> findById(UUIDTenantId id)
connacted with @Introspected
annotation works fine.
I think this works as expected.
Expected Behavior
findById
repository method not works when key is UUID - it works couple versions ago. In my case it is composit keyrepository
OperationLog entity:
Actual Behaviour
Steps To Reproduce
No response
Environment Information
Example Application
No response
Version
4.6.2