Internal Website Search

and roll back. T1 T2 ---------------------------------------------------------- READ(A) version =1 value=0 | READ(B) version =1 value=0 | | READ(A) version =1 value=0 | READ(B) version =1 value=0 | B = A + B + 20 | WRITE(B) version =2 value=20 A = A + B + 10 | WRITE(A) version =2 value=10

javax.persistence.NamedQuery; import javax.persistence.Query; import javax.persistence. Version ; import ... id = "1"; @SuppressWarnings("unused") // used by JPA @ Version private int version ; @Basic protected ... javax.persistence.ManyToOne; import javax.persistence.MapsId; import javax.persistence. Version

/SystemDB.odb db/SystemDB.odb.rpmnew ObjectDB Doctor [ version 2.6.3] Copyright (c) 2015, ObjectDB Software ... fields will cause the corruption? An example would be beneficial. Also, can we assume that all version prior to 2.6.4_02 have this problem? In particular version 2.5.5_14 and 2.6.1_05? Thank you Emil

.jboss.modules] JBoss Modules version 1.0.1.GA 13:49:14,316 INFO [org.jboss.msc] JBoss MSC version 1.0.0 ... ) Deploying JDBC-compliant driver class org.h2.Driver ( version 1.2) 13:49:22,868 INFO [org.jboss.as ... service thread 1-1) JBoss Remoting version 3.2.0.Beta2 13:49:24,513 INFO [org.xnio] (MSC service thread

after upgrading to 2.9.0 (because of the other problems in former versions ), the database destroys ... the engine that manages the database storage, at least in the last 2 years, so there is nothing in version 2 ... there was a situation in which more than one process accessed the database? Again, version 2.9.0 uses exactly

; homplex@homplex01:~$ java - version java version "1.6.0_18" OpenJDK Runtime Environment (IcedTea6 1 ... + agent homplex@homplex01:~$ java -javaagent:/home/homplex/objectdb/objectdb.jar - version java version "1 ... -Dcom.sun.management.jmxremote.authenticate=fals -versionjava version "1.6.0_18" OpenJDK Runtime

Hi, I've been getting the following exception when trying to query ObjectDB in server mode version ... . The number 36 indicates type version number 36 (i.e. after 35 modification of some entity type). You have an object with that type version number but the type version doesn't exist in the database

enhanced additional getters/setters, because the additional methods now use (since about version 2-6 ... the method as a setter or getter), prior to version 2-6-5: [accessor_name]_odbHidden_ Where [accessor ... ; http://www.objectdb.com/object/db/database/ version /2-6-5     - Renamed internal

. However, the test case on that forum thread still passes with the last ObjectDB version . ObjectDB maintains a version number for every entity object, which is increased on every update. An  OptimisticLockException  is thrown when that version number indicates a concurrent update by another user (using

javax.persistence.NamedQuery; import javax.persistence.Query; import javax.persistence. Version ; import ... "; @SuppressWarnings("unused") // used by JPA @ Version private int version ; @Basic protected java.lang.Integer ... .persistence. Version ; @Entity @IdClass(CompoundKeyMapItem.CompoundKeyMapItemId.class) public class

sure the enhancement script runs the same objectdb.jar library version that the program runs with. I ... yet tried versions between objectdb-2.6.3_04 and objectdb-2.6.6_07 (bracketing to find which one broke it). But I know that I can't run any of my objectdb-based programs using a version later

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

.persistence.Temporal; import javax.persistence.TemporalType; import javax.persistence. Version ; public ... ; private Long version ;         private Date startDateTime;   ... (other.getId()) && version .equals(other.getVersion());         }   

. Which ObjectDB version are you using? Try the last ObjectDB version , which should fix this issue ... them again, or use an ObjectDB version before the fix, with an UPDATE queries that change the IDs ... _02 version in our test enviroment. I think we have a different issue from the one in the forum

is considered temporary. Version 3.x (currently in development) will add better support for large ... .     support Support the new version caused an unexpected exception [ObjectDB 2.8.7_05 ... .JpaQuery.getResultList(JpaQuery.java:726) btc_es BTC EmbeddedSystems the previous version 2.8.7_04

get this stack: 13:52:01,121 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA 13:52:01,304 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA 13:52:01,347 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting 13:52:01,959 INFO  [org.xnio] XNIO Version 3.0.3.GA 13

:757) I checked multiple times if the versions match. They do. DB server version 2.6.2. Client version 2.6.2. Also there's only one objectdb jar on the classpath. It's also not a network problem ... if different ObjectDB versions are in use on the client and on the server, but such exceptions

can be null Since: JPA 2.0 boolean isVersion () Is the attribute a version attribute. Return: boolean indicating whether the attribute is a version attribute Since: JPA 2.0

JPA Annotation AssociationOverrides Target: TYPE, METHOD, FIELD Implemented Interfaces: Annotation Used to override mappings of multiple relationship properties or fields. Example: @MappedSuperclass public class Employee { @Id protected Integer id; @ Version protected Integer version ; @ManyToOne

: @MappedSuperclass public class Employee { @Id protected Integer id; @ Version protected Integer version

JPA Method in javax.persistence.metamodel.IdentifiableType boolean hasVersionAttribute () Whether the identifiable type has a version attribute. Return: boolean indicating whether the identifiable type has a version attribute Since: JPA 2.0

using bulk update operations must manually update the value of the version column, if desired, and/or manually validate the value of the version column. The persistence context is not synchronized

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

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

primitive types and wrapper types as equivalent. Note that Id attributes, version attributes

conversion of the following: Id attributes, version attributes, relationship attributes

-Georg Zwicker What version of ObjectDB are you using? Any additional information related ... .7.1_01 in our app, the doctor is the version from march 2016. Database file is around 35 GByte, how can we handle that ? hgzwicker Hans-Georg Zwicker Is it the Doctor of version 2.7.0_01? If not

the issue! It works fine now. btc_es BTC EmbeddedSystems Hello, if we use the version 2.7.4_04 ... listeners for pre persisted and post persisted in order to check the entity version number. For example a new entity is created (entity version = 0), pre persisted (entity version = 0), post persisted

it will report: Java/JVM version : 1.8 Java/JVM detail version : 1.8.0_74 ObjectDB enhancer: begin ... (Element.java:1) ... 21 more To compare with objectdb-2.6.3_04.jar Under /lib there are 2 versions ... that version during enhancement (use File view mode not Project view mode in NetBeans to find

. In the current implementation ObjectDB is embedded in the driver. Any 2.x version of the driver ... is fixed for all 2.x versions . However, since the client-server protocol is occasionally being updated, there should be a match between the ObjectDB BIRT client-server protocol version and an ObjectDB

is much more complex and could easily be inaccurate. Future version of ObjectDB will probably ... Support we implemented version 2.8.0_02, added:             ... query: ( version 2.7.6 it takes 47 ms, version 2.8.0_02 it takes 700 ms): SELECT DISTINCT o.parentNode

Zwicker The new ObjectDB version will be released today or tomorrow morning. No problem with broken references, if their existence is planned and managed by the application. support Support Version 2.7.2 includes the changes that are specified on #15 above. Please run the Doctor of the new version

environment, but now in field. Object DB version was upgraded maybe two times in the last months in ... version 2.8.4 that fixed that issue. support Support I think the schema may changed 2-5 times ... ; ... itsme Martin Petzold It is usually difficult to know the total number of schema versions

you for this report. support Support Version 2.8.8_03 should throw an exception with the correct ... whether it is also solved. support Support With version 2.8.8_03 we get another exception stack trace ... btc_es BTC EmbeddedSystems The exception in #6 is similar to #1, so apparently version 2.8.8_03

versions (2.4.7, 2.4.6). If it is a new problem, we may be able to track the change the causes it. support ... for a item thats not in the db.   Stefan Stefan Mair The problem is in version 2.4.7. I will try with an older Version on Monday. Stefan Stefan Mair The 256 observation is interesting

Dear Support Team Changing objectdb from version 2.7.4 to version 2.8.1 I found, that query against embedded objects doesn't work as expected and the formerly green UnitTest ( Version 2.7.4) turns red ( Version 2.8.1). For what I thought I realized is, that the version 2.8.1 was sensitive

JDO Method in javax.jdo.spi.StateManager Object getVersion (   PersistenceCapable pc ) Return the object representing the version of the calling instance. Parameters: pc - the calling PersistenceCapable instance Return: the object representing the version of the calling instance Since: JDO 2.0

JDO Enum VersionStrategy java.lang.Object ∟  java.lang.Enum ∟  javax.jdo.annotations.VersionStrategy Enumeration of the version strategy values. Since: JDO 2.1 Enum Constants DATE_TIME Since: JDO 2.1 NONE Since: JDO 2.1 STATE_IMAGE Since: JDO 2.1 UNSPECIFIED Since: JDO 2.1 VERSION _NUMBER

JDO Static Method in javax.jdo.JDOHelper Object getVersion (   Object pc ) Return the version of the instance. Parameters: pc - the instance Return: the version of the instance Since: JDO 2.0

(Object pc) Return the version of the instance. Parameters: pc - the instance Return: the version

can set the object id, version , BitSet of loaded fields, and BitSet of modified fields ... jdoDetachedState[1]: the Version of the instance jdoDetachedState[2]: a BitSet of loaded fields

(PersistenceCapable pc) Return the object representing the version of the calling instance. Parameters: pc - the calling PersistenceCapable instance Return: the object representing the version

JDO Method in javax.jdo.spi.PersistenceCapable Object jdoGetVersion () Return the version of this instance. Return: the version Since: JDO 2.0

. Parameters: in - the input Since: JDO 1.0 String toString () Return the String version of the key. Return

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

JDO Method in 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

JDO Method in 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

of the candidate class. The String... version of the method binds the named expressions in turn

getVersion (Object pc) Return the version of the parameter instance. Instances unknown by

JDO Method in 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. Return: a copy of the ObjectId of the parameter instance as modified in this transaction. See Also: PersistenceCapable() Since: JDO 2.0