About version

151-160 of 200Refresh
JDO Doc
2

addSubquery(sub, variableDeclaration, candidateCollectionExpression, parameter)

Method javax.jdo.Query void addSubquery(   Query sub,   String variableDeclaration,   String candidateCollectionExpression,   String parameter ) Add a subquery to this query. The String version of the method binds the named expression to the parameter implictly or explicitly declared in
JDO Doc
2

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
2

addSubquery(sub, variableDeclaration, candidateCollectionExpression, parameters)

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

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
JDO Doc
2

toString()

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

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
Forum
2

Failed to read DB file while online backup is running

to finish its task. The version of ObjectDB I am running is 2.6.1.b02 Any idea what is causing ... will be observing it with the new version. Unfortunately the "Failed to read from file '/path_to_db/dbFile.odb ... order to explore this issue, including range of affected ObjectDB versions. I finally got
Forum
2

Possible cause for "Enhancement of type ... is old and cannot be used"

objectdb.jar library version that the program runs with. I am certainly not 'adding a persistent field to a super class' in any of these cases. I have not yet tried versions between objectdb-2.6.3_04 ... of my objectdb-based programs using a version later than objectdb-2.6.3_04 (other than the very basic ObjectDB
Forum
2

problems using the explorer

we are currently evaluating objectDB. Environment OSX 10.9.2, JavaSE-1.7 Version: Kepler Service ... > com.objectdb objectdb <version>2.2.5version> ...   Problem: we created a small example that just writes and retrieves
Forum
2

Recommendation - concurrent access multiple class v

that it might get corrupted because the manual says that we must not access ObjectDB with different versions ... , where the previous version of a class is used by some servers, then others come with the new version, then finally all of them get the new version? So...basically...concurrent access with version x and version x