[
https://issues.apache.org/jira/browse/FINERACT-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203434#comment-17203434
]
Petri Tuomola commented on FINERACT-1161:
-----------------------------------------
Hi
If you write derived JPA queries that are completely wrong - i.e. refer to
non-existent columns - you do get an exception when starting. So we shouldn't
have any of those.
There's a problem with custom queries - these are not checked at startup time,
and we have had a number of problems with these (e.g. missing named bind
variables as these seem to be treated differently in Hibernate vs OpenJPA).
Unfortunately I don't know of any way to get them checked - except to run tests
that exercise all of them :)
Then there's this case. To be honest I'm not quite sure why this was not
working, as I think the syntax is valid as per JPA - you should be able to link
to a nested object using its ID. So that's probably why Spring JPA did not
complain about the syntax of the query. But for some reason OpenJPA doesn't
return any matching records when you use this.
I have to confess I didn't start debugging this in more depth as the fix seemed
trivial: we had the nested objects available and using them as parameters to
the query resulted in the right records being returned...
> Update & delete of notes not working
> ------------------------------------
>
> Key: FINERACT-1161
> URL: https://issues.apache.org/jira/browse/FINERACT-1161
> Project: Apache Fineract
> Issue Type: Bug
> Reporter: Petri Tuomola
> Assignee: Petri Tuomola
> Priority: Major
> Fix For: 1.5.0
>
>
> Update & delete operations on notes are not working, as Fineract can't find
> the note to update even though it exists. Caused by incorrect NoteRepository
> JPA interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
