Home » Search

About YEAR

51-60 of 63Refresh
Issue
1

Sometimes the ObjectDB throws an internal expeption if a persist() was executed

status is active since one year. But its not an ObjectDB issue. The problem is just that we started
Forum
1

user defined backup target

some of them doesn't even really care about database and backup-files at all), so over the years
Forum
1

Wrong data stored in time only fields

.getInstance();         calendar.setTime(rondedDate);                 calendar.set(Calendar.YEAR, 1970
Forum
1

Future JDO versions?

versions: http://db.apache.org/jdo/specifications.html ?   Development of JDO in the recent years
Forum
1

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 for a superb
Issue
1

Unexpected error when loading all entity instance

should fix this bug. This is probably the most critical bug in ObjectDB in the recent years. Thank
Forum
1

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
Forum
1

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

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

signatures I provided worked fine (and have for years before) with ObjectDB with objectdb-2.6.3_04
Forum
1

java 8 LocalDateTime is not working in query

.    After now three years, why does ObjectDB still not support new Java 8 date and time API and also not