ObjectDB Database Search

don't know why). You are using version 1.0.3 which is almost 7 years old. Many bugs have been fixed

legacy, developed by two handred people by sevral years so i and my friend engaged in that rescue

datastore i.e. about 600ms rather than 3 seconds (on a 4 years old i3 based computer). We also tried

Hi, I know that this has been asked, but the last time seems to be two years ago, so I'd like to know whether there is a change or an outlook regarding the topic: Is it possible, or planned, to run ObjectDB purely in-memory, without a any file on disk? Note that "file on RAM disk

Just ran into a problem that I've not seen in 10 years of running ObjectDb: java.lang.IllegalArgumentException Attempt to refresh a non managed entity object (error 635) Nothing changed in my code, but I'm wondering if there is a problem with the config file, and /or my recent experiments

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. This is probably the most critical bug in ObjectDB in the recent years . Thank you very much for your report and for your help in reproducing the situation. support Support

is more than two years old.     support Support This report seems to be related to issue

an IoT device.  It has to be able to run for months if not years without maintenance. I hope

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

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

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

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

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

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

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