ObjectDB Database Search

- Can you please let me know the latest version maven entry i got confused as the downloads have version in ... full blown version where we could test it properly. If there are any cost implications on the version ... The last version on Maven is also 2.5.2. Please clarify your question. Prices of ObjectDB licenses

we tried (you have our example database form former issues) the latest version , did a statics ... .objectdb.com/forum/2845 for queries we are using hgzpincher Hans-Georg Zwicker Version 2.8.9_01 ... in version 2.8.9_02 but maybe there is another relevant query performance regression

of objectdb-2.6.9_02 in a Glassfish web app. Can see correct version of objectdb-2.6.9_02 ... with an Ant script) Object clearly indicates the version . Q: How can one interrogate objectdb for the version at run-time ? It does not seem to be in the odb logs, and turning on the debug mode does not

!  I hadn't noticed this because the maven instructions still show the old version , and the new version does not seem to be in that repository... or at least I can't get my compiler ... is back!  But with an updated version this time!  Here is updated (and filtered

Is there some way of telling, just from an obd database file, what version it is?   dmoshal David Moshal An ObjectDB 2.x database file has no version , at least from the point of view of ObjectDB users. You should be able to use the same database file with different versions of the ObjectDB 2.x software. support Support

.thondavada Saiprasad Thondavada It’s good to see that a 10-year-old version of ObjectDB ... releases are designed so that databases created in earlier 2.x versions can still be opened and used in later 2.x versions , and the API remains largely consistent. In theory, your existing applications

new and future JDO versions : http://db.apache.org/jdo/specifications.html ?   sjzlondon ... and JDO at the same time in a future version of ObjectDB. Same is regarding automatically generated

the ObjectDB Doctor of version 2.2 in repair mode on existing database files, and to switch to the new database files that are generated by the Doctor when moving to version 2.2. support Support

Using the current version of persistence.xml leads to an error: com.objectdb.jpa.Provider org.xml.sax.SAXParseException; lineNumber: 10; columnNumber: 135; cvc-elt.1: Cannot find the declaration ... .createEntityManagerFactory(Persistence.java:54) but reverting to version 1.0 makes the error go away

In earlier versions this query worked fine. In version 2.5.2_05 does not work .orderBy(cb.desc(cb.greatest(root.get("createDate").as(Date.class)))).distinct(true) Thank you for your help. galandor Orlov Sergey Please try build 2.5.2_06 that should fix this regression (of casting to Date ). support Support

Hello i would like to use objectDB in Free Version until its not getting in Productive phase... Now my (maybe Stupid) Question because i did not found a good definition. How Do you (for the Free ... . If you buy a server or a site license you have it for life, including update to the same major version (e.g. all 2.x updates). support Support

ObjectDB 2.1 has been released and it includes important additions and fixes: Added Online Backup utility ( issue #16 ). Added Master-Slave  Replication / Clustering (issue #17 ). Added a PDF version of the ObjectDB manual (included in the download). Added sample (tutorials) Maven projects

Hi, Do we have any mechanism to knwo whether the odb file belongs to 1.x object db or 2.x object db. Before migrating all the odb files from objectdb 1.x to 2.x, i would like to add a check if it is already migrated. Any API which is exposed to check the odb files version  ? binitbhaskar Binit

I have a legacy production environment that is running "jre1.6.0_16". I am trying to upgrade from 1.0.4 to the latest.   Thanks for your time. bmcalist Brian McAlister Current ObjectDB versions are tested with JDK 1.7, so JDK 1.7 or later should be fine. Maybe it can also work with JDK 1.6 but it has not been tested recently. support Support

' (object has version 125 instead of 126) (error 673) at com.objectdb.jpa.EMImpl.beforeCompletion(EMImpl

I have defined a number of JDO indexes on my persistent class, so would like to know which is the preferred version of JDO to use e.g. is it jdo-api-3.1.jar? Thank you paul Paul Hudson ObjectDB 2.x uses JDO 2.2. support Support

deadlock with newest version 2.4.4_16

Memory Leaks after COMMIT operation (checked on versions 2.6.5 & 2.6.6.b01)

ObjectDB version 2.3 has been released

there is a free version?

Which version to use with Glassfish ?

Waterfall tree algorithm for more optimized version of objectdb or

Version 2.2.7 build 7/8 issue

ObjectDB manages automatic entity versioning (for optimistic lock purposes). Every entity object modification is reflected by a new version number. Naturally, previous values in the entity object ... to go back in time and view old versions (and old values) of entity objects. Future versions of ObjectDB

{ String filename } If I call this method (all classes are enhanced) the version of the event does not ... solve the core issue. Will there be a fixed version anytime in the near future? Thanks in advance

There seems to be a bug in the JDOQL processor in recent versions of ObjectDB. I've uploaded a "laptop" example to demonstrate the problem. The query in Test1.main should return "ThinkMachine MAX SX 20", but it returns incorrect "Media Central Media 555". Earlier versions (at least up to 2.5.4

Version 2.8.4 fixes a critical bug that in rare cases may cause collision between different schema versions of entity classes, when schemas have changes many times (usually more than 20 times). This bug mainly affects queries on hierarchy of multiple entity classes (i.e. a query on a super class

Can't deploy objectDB ver 2.4.5 or later using GlassFish 3.1.2, NetBeans 7.2.1 Win 7 & 8. ObjectDB Version 2.4.4 is working good. [#|2012-12-18T05:26:53.167-0800|SEVERE|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=44;_ThreadName=Thread-2;|java.lang

.OPTIMISTIC on a versioned object, the entity manager must ensure that neither of the following ... of type LockModeType.OPTIMISTIC_FORCE_INCREMENT on a versioned object, will also force an update (increment) to the entity's version column. The persistence implementation is not required to support

protected Integer empId; @ Version protected Integer version ; @ManyToOne @JoinColumn(name = "ADDR ... to FTEMPLOYEE.EMPID // Inherited version field mapped to FTEMPLOYEE. VERSION // Inherited address field ... _EMP.EMPID // Inherited version field mapped to PT_EMP. VERSION // address field mapping overridden

to the version attribute declared by the entity or mapped superclass. Parameters: type - the type of the represented declared version attribute Returns: declared version attribute. Throws: IllegalArgumentException - if version attribute of the type is not declared in the identifiable type. Since: Jakarta Persistence (JPA) 1.0

SingularAttribute getVersion (    Class type ) Return the attribute that corresponds to the version attribute of the entity or mapped superclass. Parameters: type - the type of the represented version attribute Returns: version attribute. Throws: IllegalArgumentException - if version attribute

) Return the version of the entity. A generated version is not guaranteed to be available

Since: Jakarta Persistence (JPA) 1.0 boolean isVersion () Is the attribute a version attribute? Returns: boolean indicating whether the attribute is a version attribute. Since: Jakarta Persistence (JPA) 1.0

the value of the version column, if desired, and/or manually validate the value of the version column

Integer id; @ Version protected Integer version ; protected String address; public Integer getId

; @ Version protected Integer version ; @ManyToOne protected Address address; @OneToOne protected Locker

the specified options . If a pessimistic lock mode type is specified and the entity contains a version attribute, the persistence provider must also perform optimistic version checks when obtaining ... call is made. OptimisticLockException - if the optimistic version check fails. TransactionRequiredException

and the entity contains a version attribute, the persistence provider must also perform optimistic version ... lock call is made. OptimisticLockException - if the optimistic version check fails

properties. If a pessimistic lock mode type is specified and the entity contains a version attribute, the persistence provider must also perform optimistic version checks when obtaining the database ... call is made. OptimisticLockException - if the optimistic version check fails

and the entity has a version attribute, the persistence provider must perform optimistic version checks ... version check fails. TransactionRequiredException - if there is no transaction and a lock mode

within the persistence context and the lock mode type is pessimistic and the entity has a version attribute, the persistence provider must perform optimistic version checks when obtaining the database ... . PersistenceException - if an unsupported lock call is made. OptimisticLockException - if the optimistic version check

has a version attribute, the persistence provider must perform optimistic version checks ... call is made. OptimisticLockException - if the optimistic version check fails. TransactionRequiredException

is pessimistic and the entity has a version attribute, the persistence provider must perform optimistic version checks when obtaining the database lock. If these checks fail ... version check fails. TransactionRequiredException - if there is no transaction and a lock mode

Jakarta Persistence (JPA) Method in jakarta.persistence.metamodel.SingularAttribute boolean isVersion() Is the attribute a version attribute? Returns: boolean indicating whether the attribute is a version attribute. Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Method in jakarta.persistence.metamodel.IdentifiableType boolean hasVersionAttribute() Whether the identifiable type has a version attribute. Returns: boolean indicating whether the identifiable type has a version attribute. Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Method in jakarta.persistence.PersistenceUnitUtil Object getVersion (    Object entity ) Return the version of the entity. A generated version is not guaranteed to be available until after the database insert has occurred. Returns null if the entity does not

would otherwise apply. The Convert annotation should not be used to specify conversion of id attributes, of version

never applies to id attributes , version attributes , relationship attributes, or to attributes explicitly

of the entity. An entity class may optionally have a field or property annotated Version , which holds