Internal Website Search

81-90 of 114 resultsRefresh

em.flush(); em.clear(); loosing data and not persisting managed objects

the length of primary keys, but large strings as demonstrated by this test should be avoided, if possible, because a primary key whose length is larger than about 45 bytes is much less efficient.

Query in JPA2 with LEFT JOIN on INNER JOIN

Selection[profiles.length+1]; Selection<String> ... ); masterPredicate = cb.and(masterPredicate,predicateOnPath); for (int i = 0; i < profiles.length; i

ODB IndexActivation NullPointerException

Thread[threadSet.size()]); for (int i = 0; i < threadArray.length; i++) {     ... :#ff0000;">pos = 3987456 length = 2048 12.07.2017 16:43

Error using query with MAX() function

strings in any length that is supported by Java (i.e. up to 2GB). Your test case

Bug: ClassCastException by retrieval

; int iLen = ca.length;   Character[] la = new Character[iLen];   for (int ii = 0; ii <

Problem of query With an aggregate function

;(); for (BigDecimal[] bigDecimals : listRes) { for (int i = 0; i < bigDecimals.length; i

NullPointerException using with "refresh" method

with zero length files using atomic moves, and after a power loss. Maybe you should also check ... sources: -

Page cache File handling produced an Negative seek offset

on std error: pos = -8192 length = 8192   pos = -8192 length = 8192

Unexpected Exception (Error 990) with ArrayIndexOutOfBoundsException

out of bounds for length 0 java.lang.ArrayIndexOutOfBoundsException: Index 5 out of bounds for length 0

Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct)

=deep float quantity (length)], [class=IntegerQuantity][project=TEST: project 1][id=47][name=deep ... =FloatQuantity][project=TEST: project 1][id=46][name=deep float quantity (length)]) INFO: ConfigBean