Home » Search

About version

141-150 of 200Refresh
JDO Doc
1

addSubquery(sub, variableDeclaration, candidateCollectionExpression, parameters)

Method javax.jdo.Query void addSubquery(   Query sub,   String variableDeclaration,   String candidateCollectionExpression,   Map parameters ) Add a subquery to this query. The Map version of the method treats the key of each map entry as the name of the parameter in the subquery, with or
JDO Doc
1

addSubquery(sub, variableDeclaration, candidateCollectionExpression, parameters)

is the extent of the candidate class. The String... version of the method binds the named expressions in turn
Forum
1

Conflicting modifiers .... (javax.persistence.Id, javax.persistence.ManyToOne)

.persistence.Version; import uk.co.his.experiment8.common.TestException; @Entity @NamedQueries ... @Version private int version; @Basic protected java.lang.Integer lastInstanceInMap; protected ... ; import javax.persistence.Version; @Entity @IdClass(CompoundKeyMapItem.CompoundKeyMapItemId.class
JDO Doc
1

getVersion(pc)

Method javax.jdo.spi.StateInterrogation Object getVersion(   Object pc ) Return the version of the parameter instance. Instances unknown by the implementation return null. Parameters: pc - the instance. Returns: a copy of the ObjectId of the parameter instance as modified in this transaction. Since: JDO 2.0 See Also: PersistenceCapable.jdoGetVersion()
JPA Doc
1

LockModeType.OPTIMISTIC_FORCE_INCREMENT

Enum Constant javax.persistence.LockModeType OPTIMISTIC_FORCE_INCREMENT Optimistic lock, with version update. Since: JPA 2.0
JPA Doc
1

LockModeType.PESSIMISTIC_FORCE_INCREMENT

Enum Constant javax.persistence.LockModeType PESSIMISTIC_FORCE_INCREMENT Pessimistic write lock, with version update. Since: JPA 2.0
Forum
1

ODB IndexActivation NullPointerException

are built in the background starting version 2.6.6, and apparently the last related code change was in ... build 2.6.9_08 is "ODB-IndexActivation" (it was "ODB IndexActivation" until version 2.6.9_07 ... the version 2.6.1 and waited for a new version to fix. Unfortunatly the new version 2.7-1_01 does
JDO Doc
1

toString()

Method javax.jdo.identity.ByteIdentity String toString() Return the String version of the key. Returns: the key. Since: JDO 1.0
Forum
1

Visibility of changes in Transaction is not visible to a JPA QL Query

; @Id private String id; @Version private int version; @Basic private Integer property ... );   } public Integer getJPAVersion() {   return version; } public String getCachedKey() {   return ... =" + id + ", version=" + version + ", key=" + cachedKey + ", property=" + property; } public
Issue
1

again merger missing logs + objectdb exception

. is there a problem to have this kind of broken references ? The new ObjectDB version will be released today or ... the application. Version 2.7.2 includes the changes that are specified on #15 above. Please run the Doctor of the new version (2.7.2) to repair the database. If you have a daily backup that you can run