10 | em.flush(); em.clear(); loosing data and not persisting managed objects should fix it. As a side note - ObjectDB doesn't limit the length of primary keys, but large strings as demonstrated by this test should be avoided, if possible, because a primary key whose length |
10 | Query in JPA2 with LEFT JOIN on INNER JOIN<Action> root = cq.from(Action.class); Selection[] selections = new Selection[profiles.length+1 ... i = 0; i < profiles.length; i++) { Join <Action,ActionProfile> actionJoinActionProfile = root |
10 | ODB IndexActivation NullPointerException < threadArray.length; i++) { if (threadArray[i].getName().equals(indexActivationThreadName ... :33 | changed: Peter Gegner, Anschrift: Gegnerweg 1, 10119 Berlin pos = 3987456 length = 2048 12 |
7 | Error using query with MAX() function strings in any length that is supported by Java (i.e. up to 2GB). Your test case demonstrates |
7 | Bug: ClassCastException by retrieval) { this.sData = sData; char[] ca = sData.toCharArray(); int iLen = ca.length; Character[] la |
7 | Problem of query With an aggregate function) { for (int i = 0; i < bigDecimals.length; i++) { listSommeLong.add(bigDecimals[i |
2 | NullPointerException using with "refresh" method with zero length files using atomic moves, and after a power loss. Maybe you should also check ... : - https://thunk.org/tytso/blog/2009/03/12/delayed-allocation-and-the-zero-length-file-problem/ - https |
2 | Page cache File handling produced an java.io.IOException: Negative seek offsetwe get following exception when we execute a find() in a scenario, we can not readjust with an example. Before the exception throws we get two outputs on std error: pos = -8192 length = 8192 ... : (Now there are other line Numbers in PAG.java) pos = -8192 length = 8192 [ObjectDB 2.6.7 |
2 | Unexpected Exception (Error 990) with ArrayIndexOutOfBoundsException.ArrayIndexOutOfBoundsException: Index 5 out of bounds for length 0 java.lang.ArrayIndexOutOfBoundsException: Index 5 out of bounds for length 0 at com.objectdb.o.UTY.L(UTY.java:1440) at com.objectdb.o.ENH |
2 | Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct) (length)], [class=IntegerQuantity][project=TEST: project 1][id=47][name=deep integer quantity ... : project 1][id=46][name=deep float quantity (length)]) INFO: ConfigBean []: testQuery: element.ownedElement |
