Internal Website Search

51-79 of 79 results

Entity object parameter in Explorer parameter

, With all respect, the explorer app is really bad. When I ordered objectdb about four years ago

Wrong data stored in time only fields

(Calendar. YEAR , 1970);         calendar.set(Calendar.MONTH, Calendar

Activation Issue

the Retrieving Metamodel without Connection feature (which was implemented following your request two years ago

doctor error message after database getting page errors

several critical bugs that may cause various unexpected states have been fixed in the recent years

Setting temp directory location in ObjectDB

was released many years ago when Java didn't provide a standard file locking). ObjectDB 1.x is now

Feature Request: Improved ObjectDB Explorer

of the Explorer was developed about 15 years ago, and although it was adjusted to ObjectDB 2.0 and JPA, the look

user defined backup target

and backup-files at all), so over the years there will be Terabytes of useless old backup files

Roadmap - no progress - any plans - transparency?

the first years after the release of version 2.0, many critical bugs have been fixed. We are working

ObjectDB 2 has been released and is now more affordable

Today, after years of hard work, ObjectDB 2.0 was released and is available for download. In addition, in order to make ObjectDB more affordable, the pricing model was changed: The prices of the Server, Site and OEM licenses were sharply reduced. ObjectDB 2.0 licenses will now include free updates

Recovery file does not match db file

delete it and restart the database server. Version 2.3.1 is nearly one year old - you should upgrade

What role is the JDO in ObjectDB?

, and if it had been introduced three years later, it might have been better accepted by a developer

Database Inconsistency or corruption

. There is no open issue in ObjectDB (and there was none in the last years ) that may cause this issue

Opensource ObjectDB

I know you have answered this question some years ago, but I think about the databases that have recently "triumphed" like MySQL, MongoDB or SQLite and they are free databases. Also in the Java world we have the example of Hibernate (ORM) and Apache Hadoop (framework for Big Data). In my opinion

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

to the new public method." At one stage, some years ago when I was using EclipseLink, I was using

Remove an entity which attributes were changed - OptimisticLockException

both plugins are identical. I checked all of this with a debugger.   We had a similar issue last year 2015

PersistenceException: Failed to locate field

years ago because of some issue which I believe may have been related to my use of groovy instead

Compile time enhancement using build.xml of a Netbeans web application

depth or adapt a build.xml for some years , and am not an expert with ANT. A complete example

Upgrade to Java 8 won't run

I've been using ObjectDB with Groovy 2.1 and Java 7 for nearly a year .  Today, I updated everything to the latest revs (Groovy 2.3.6, Java 1.8.0_25, and ObjectDB 2.5.7_05), and now my application fails when opening the database. It's dying on one of these lines: emf = Persistence

How to develop for a server license

;for one month, then the servers will be recycled. After half a year , we need to use the license

Free version limitation and upgrading

Only the OEM license (which let you distribute ObjectDB to others) is renewed every year

query hint

some years ago there was a chat around query hints http://www.objectdb.com/issue/2417 we are currently trying that with the latest version but we do not see that our hint is used this is the query: SELECT DISTINCT o from ObjectNode o join o.properties p1 join o.properties p2 join o.properties p3

ObjectDb JDK8-11 support

The recommended version is 2.8.4. Version 2.6.1 is 5 years old, and many improvements as well as bug fixes

InternalException when using MEMBER OF on a large list in a query

. A similar issue was fixed a few years ago and since then this is the first report. First, please check

java 8 LocalDateTime is not working in query

will be implemented by objectdb soon.    Joe Joe Khan After now three years , why does ObjectDB still not

Objects are not garbage collected

(e.g. from a year or two ago) with which the memory is released in this specific case? support

ObjectDB-2.6.9: Failed to commit transaction: Failed to set numeric value of field property Element.id using reflection

worked fine (and have for years before) with ObjectDB with objectdb-2.6.3_04. You now say

'DROP TABLE' in ODB?

in a new Explorer, which is on our roadmap, but not for the next year . support Support Any Update

JPA 2.2 LocalDate still not working

Hello, I would have commented in this Thread but somehow I wasn't able to. Now again 2 years later and objectdb still does not support LocalDate? com.objectdb.o._RollbackException: Failed to commit transaction: Attempt to store an instance of a non persistable type java.time.LocalDate or am I

ObjectDB 2.2.9

Added new configuration to enable / disable auto serialization of non persistable types (now disabled by default). Added support of date methods ( YEAR , MONTH , DAY , HOUR , MINUTE , SECOND ). Added support of  bypassing no arg constructors  of entity classes . Added support of using