ObjectDB ObjectDB

Internal Website Search

121-130 of 200 resultsRefresh
5

Failed to read the value of field using reflection (error 363)

that has already been fixed. The stack trace is produced by ObjectDB 2.3.7, which is 2 years old now, and many issues have been fixed in the last 2 years. Please try switching to the last ObjectDB version. It is also recommended that you check the database file with the ObjectDB Doctor, and use it to fix
5

NegativeArraySizeException on commiting a transaction

, but the same error is happening also on the fixed DB file. Btw. during fixing the DB file an Internal error was thrown (details here: http://www.objectdb.com/database/issue/285 ), but the fixing went ... Thank You for the fix. We will consider reorganizing our data structures, but with this raise we will have enough time to plan it carefully. jakab Gergely Jakab
5

Left join fetch behaviour doesn't retrieve children?

you for this report. Build 2.6.2_03 should fix this issue. support Support Thx you support ! That's perfect ... that the relationship is activated. The unit tests were also fixed following your report. support Support ... . Please try build 2.6.2_04 that should fix this issue. support Support Well, seems to be ok support
5

ODB IndexActivation NullPointerException

ObjectDB feature. Build 2.6.7_07 includes an attempt to fix this exception. Please try it. support ... EmbeddedSystems Please try build 2.6.9_08 that should fix the NullPointerException. remove the printing ... and waited for a new version to fix. Unfortunatly the new version 2.7-1_01 does not fix that problem as
4

Problem on JPA Merge Entity.

and the useful test application. Please try version 2.0.5 that fixes the problem. support Support Thank ... try the version 2.0.5 and that don't fix the issue. I try it with the test application and my full application. In both case the bug is still there. Do you check if the new version fixes the problem
4

like operator (String)

. You are right, LIKE with no wildcards should function as =. Build 2.4.7_17 fixes this behavior. support Support Thanks for the quick fix. This new version 2.4.7_17 fixes this issue. pezifromvienna Peter Sauer
1

New entity objects are duplicated on merge cascading

)         private Long id;     }        } support Support Fixing this bug may require totally new implementation of merge operations. So unfortunately an immediate fix is not possible. But this issue has a high priority and hopefully will be fixed soon. support Support This bug can also cause an "Attempt
1

[ObjectDB 2.6.9] Unexpected exception (Error 990)

Try to run the Doctor to fix the production database. Do you still get the exception in production after fixing the database? support Support In production it takes about 18 hours, and finish ok! jastorga Juan This report is similar to the report in issue #1977 that was fixed now in version 2.7.1
1

ObjectDB 2.4.4

. Fixed a bug in filtering mapped by objects by type. Fixed a regression bug in using primary key fields in queries. Fixed a regression bug of duplicating new objects on merge. Fixed a Doctor bug that caused false alarms.
1

Object DB Explorer fails to open database

. Towfique Imam. mithu1408 Md. Towfique Imam There was a bug in build 2.05_03 that was fixed in build ... listeners and callback methods. Version 2.1.1 fixes this issue. support Support Thanks for the quick fix. Version 2.1.1 fixed the issue. mithu1408 Md. Towfique Imam

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support