ObjectDB Database Search
51-80 of 80 resultsIs there an update on running ObjectDB purely in-memory? 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 | |
Date field Index is corrupted due to time change; calendar.set(Calendar. YEAR , 1970); calendar.set | |
Wrong data stored in time only fields(Calendar. YEAR , 1970); calendar.set(Calendar.MONTH, Calendar | |
500Mb ObjectDb database opening issue datastore i.e. about 600ms rather than 3 seconds (on a 4 years old i3 based computer). We also tried | |
Incremental online backup incremental backup later this year . support Support Great news. Does this plan also include | |
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 | |
Database Inconsistency or corruption. There is no open issue in ObjectDB (and there was none in the last years ) that may cause this issue | |
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 | |
PersistenceException: Failed to locate field years ago because of some issue which I believe may have been related to my use of groovy instead | |
Composite index support collection requests and currently costs £2,400/ year . support Support | |
Excellent support After years of evaluation and development using objectdb, we are finally about to release a product. There have been bugs to deal with, but we have stayed with objectdb because it is as fast as it promises, and the support when we have had problems has been first class. Thanks | |
Entity object parameter in Explorer parameter, With all respect, the explorer app is really bad. When I ordered objectdb about four years ago | |
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 | |
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 | |
Performance of "InsertTest" You provided the "InsertTest" in the following post, and say "On Intel Core 2 Quad Q6600 (and enhancement) it persists 340,000 objects per second". Insertion Speed Rate and Batch Load Now, ten years later, I run it on Intel Core i5-5300U (2.3Ghz) with 8GB memory, output is 45000 per second | |
Cannot connect with client they are, since the update of that version was from last year . How do I find out exact I'm running | |
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 | |
doctor error message after database getting page errors several critical bugs that may cause various unexpected states have been fixed in the recent years | |
URGENCY, or in query does not report any objects on first operand having no results? support Support it does not happen with 2.7 (it was working for years ) 2.8.9 not checked | |
Error whilst running is more than two years old. support Support This report seems to be related to issue | |
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 | |
Sometimes the ObjectDB throws an internal expeption if a persist() was executed for this case? btc_es BTC EmbeddedSystems Hello, the BUG status is active since one year . But its not | |
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 | |
Unexpected error when loading all entity instance. 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 | |
Internal error an IoT device. It has to be able to run for months if not years without maintenance. I hope | |
each 1-2 days objects on some objectdb level lock/block each other would not need a change of the data model Yes, that makes sense. We will send you an invoice for one year | |
reading from table gives Unexpected exception the problem. Note, however, that many issues have been fixed since version 2.6.3 (which is more than 3 years | |
Objects are not garbage collected (e.g. from a year or two ago) with which the memory is released in this specific case? support | |
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 | |
Why does ObjectDB duplicate classes from javax.jdo:jdo-api? the objectdb.jar file. When ObjectDB 2.0 was released many years ago, one appealing point |