Home » Search

About number

121-130 of 200 Refresh
JDO Doc
2

jdoReplaceField(fieldNumber)

Method javax.jdo.spi.PersistenceCapable void jdoReplaceField(   int fieldNumber ) The owning StateManager uses this method to ask the instance to replace the value of the single field identified by number. Parameters: fieldNumber - the field whose value is to be replaced by a callback to the StateManager's replacingXXXField method Since: JDO 1.0
JDO Doc
2

jdoReplaceFields(fieldNumbers)

Method javax.jdo.spi.PersistenceCapable void jdoReplaceFields(   int[] fieldNumbers ) The owning StateManager uses this method to ask the instance to replace the values of the multiple fields identified by number. Parameters: fieldNumbers - the fields whose values are to be replaced by multiple
JPA Doc
2

le(x, y)

Method javax.persistence.criteria.CriteriaBuilder Predicate le(   Expression  x,    Number y ) Create a predicate for testing whether the first argument is less than or equal to the second. Parameters: x - expression y - value Returns: less-than-or-equal predicate Since: JPA 2.0
JPA Doc
2

lt(x, y)

Method javax.persistence.criteria.CriteriaBuilder Predicate lt(   Expression  x,    Number y ) Create a predicate for testing whether the first argument is less than the second. Parameters: x - expression y - value Returns: less-than predicate Since: JPA 2.0
Forum
2

Modifying something with Explorer -> app JPQL with Enum doesn't work anymore

are found with field type GOOD. There are 2 ways generate the bug: Immediately after a new number ... number is printed. There is a 1 minute delay set. The same as 1, but keep ObjectDB's connection open. In this case rerunning the project many times doesn't help at all. Problem: the number of entities
JDO Doc
2

newObjectIdInstance(pcClass, obj)

, the behavior must be as specified: Number or Character: the parameter must be the single field type or
Forum
2

Occasionally slow requests in load testing

we can see that most of the requests get stuck in one of 2 places: com.objectdb.o.PGC:w: line number 232 com.objectdb.o.LFL:U: line number 1068 Please see the attached callgraph examples for full stack ... .o.LFL:U: line number 1068) indicates massive access to the database file during query processing
JDO Doc
2

printStackTrace()

matches the indicated number of frames from the bottom of the stack trace of the exception
JDO Doc
2

printStackTrace()

matches the indicated number of frames from the bottom of the stack trace of the exception
JDO Doc
2

printStackTrace()

matches the indicated number of frames from the bottom of the stack trace of the exception