About settings

91-100 of 200Refresh
Manual
9

Storing JPA Entity Objects [2011-05-04]

of every reachable object or alternatively by setting automatic cascading persist. Cascading Persist Marking ... of Address, which is another entity class. Due to the CascadeType.PERSIST setting, when an Employee ... setting the ObjectDB configuration or in a JPA portable way, by specifying the cascade-persist XML
Manual
9

Logical Operators in JPQL and Criteria API

Logical operators in JPQL and in JPA criteria queries enable composition of complex JPQL boolean expressions out of simple JPQL boolean expressions. Logical Operators ObjectDB supports 2 sets of logical operators, as shown in the following table: Set 1 - JPQL / SQL Set 2 - Java / JDO AND && OR
Manual
9

JPA Persistable Types [2019-08-10]

of the entity class (i.e. the short class name excluding the package name). A different entity name can be set ... share the same class name, explicit entity name setting is required to avoid collision. Mapped ... , java.util.List, java.util.Set, java.util.Map), and that is also a good practice when working
Manual
9

Storing JPA Entity Objects

of every reachable object or alternatively by setting automatic cascading persist. Cascading Persist Marking ... of Address, which is another entity class. Due to the CascadeType.PERSIST setting, when an Employee ... setting the ObjectDB configuration or in a JPA portable way, by specifying the cascade-persist XML
Manual
9

Storing JPA Entity Objects [2019-08-09]

of every reachable object or alternatively by setting automatic cascading persist. Cascading Persist Marking ... of Address, which is another entity class. Due to the CascadeType.PERSIST setting, when an Employee ... setting the ObjectDB configuration or in a JPA portable way, by specifying the cascade-persist XML
Manual
9

JPA Persistable Types [2019-08-10]

of the entity class (i.e. the short class name excluding the package name). A different entity name can be set ... share the same class name, explicit entity name setting is required to avoid collision. Mapped ... .util.List, java.util.Set, java.util.Map), and that is also a good practice when working with ObjectDB
Manual
9

JPA Persistable Types

of the entity class (i.e. the short class name excluding the package name). A different entity name can be set ... share the same class name, explicit entity name setting is required to avoid collision. Mapped ... .util.List, java.util.Set, java.util.Map), and that is also a good practice when working with ObjectDB
Manual
9

JPA Persistable Types [2016-08-06]

of the entity class (i.e. the short class name excluding the package name). A different entity name can be set ... share the same class name, explicit entity name setting is required to avoid collision. Mapped ... , java.util.List, java.util.Set, java.util.Map), and that is also a good practice when working
Manual
9

JPA Persistable Types [2019-08-03]

of the entity class (i.e. the short class name excluding the package name). A different entity name can be set ... share the same class name, explicit entity name setting is required to avoid collision. Mapped ... , java.util.List, java.util.Set, java.util.Map), and that is also a good practice when working
JDO Doc
8

javax.jdo.FetchPlan

is initialized to the same settings as that of the PersistenceManager. Subsequent modifications ... the fetch group to the set of active fetch groups. Add the fetch group to the set of active fetch groups ... getFetchSize() Return the fetch size, or FETCH_SIZE_OPTIMAL if not set, or FETCH_SIZE_GREEDY to fetch