About version

141-150 of 200Refresh
Issue
2

Query in nested transaction returns detached entity if lazy-loaded

! It works fine now. Hello, if we use the version 2.7.4_04 then we get another issues in our test suites ... 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 (entity version = 1) and committed
Forum
2

Remove an entity which attributes were changed - OptimisticLockException

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 ... this is not the case. In order to understand the cause, please track the object version
Forum
2

Request clarification of changes to accessor enhancement policy (non-getter prefix instead of getter suffix) AND annotations

enhanced additional getters/setters, because the additional methods now use (since about version 2-6-5 ... the method as a setter or getter), prior to version 2-6-5: [accessor_name]_odbHidden ... .objectdb.com/object/db/database/version/2-6-5     - Renamed internal Enhancer hidden methods to non
Issue
2

ObjectDB BIRT Driver Update

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

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

each 1-2 days objects on some objectdb level lock/block each other

queries without any object manipulation in these threads we how have compiled with the 02 version ... to cause issues. The change in ObjectDB version doesn't look related, it may be simply the exact ... " /> version
JDO Doc
2

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
2

LockModeType.OPTIMISTIC_FORCE_INCREMENT

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

LockModeType.PESSIMISTIC_FORCE_INCREMENT

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

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