Open segalaj opened 9 years ago
Hi,
I can reproduce it on the snapshot version. It seems that it's a limitation of orientdb itself (or possibly javassist). We should consider opening the issue on their tracker https://github.com/orientechnologies/orientdb/issues
Hi, thanks for your answer. I'm not sure that come from oriendb, in fact it's possible to have column name beginning with "_" in one table.
What do you think?
Hi,
It may come from the proxy generation that orientDB is doing.
2015-03-26 13:38 GMT+01:00 Joachim Segala notifications@github.com:
Hi, thanks for your answer. I'm not sure that come from oriendb, in fact it's possible to have column name beginning with "_" in one table.
What do you think?
— Reply to this email directly or view it on GitHub https://github.com/wisdom-framework/wisdom-orientdb/issues/23#issuecomment-86493737 .
Indeed, I am pretty sure it's related to the JPA layer of orientdb. I will check with them and open an issue if that's the case.
After further investigation it seems that it is because the field name does not match the getter/setter. https://github.com/orientechnologies/orientdb/blob/master/object/src/main/java/com/orientechnologies/orient/object/enhancement/OObjectMethodFilter.java
I open an issue at orientdb https://github.com/orientechnologies/orientdb/issues/3822
Thanks a lot for your investigation.
It seems it will be fix for orientdb 2.2
Problem Get the value of an element attribute named _ return always NULL
How to reproduce Create a model like:
Try to access to an element in a controller:
Return:
Environment Java 8, wisdom 0.7.0, wisdom-orientdb 0.2.4, orientdb 2.0.2