ObjectDB ObjectDB

Internal Website Search

61-70 of 200 resultsRefresh
6

remove & persist in same transaction => Attempt to reuse an existing primary key value

. support Support ObjectDB version 2.7.0 fixes this issue. Thank you for the report. support Support Thank you for the fix. It works. btc_es BTC EmbeddedSystems Build 2.7.5_07 fixes this issue again after unknown regression. support Support A conflict was found between the fix of this issue
6

Merge Issue: Attempt to reuse an existing primary key value

are created we expect that the database will contain 2 B instances at the end of the test. Until that fix 3 B ... 2.4.6_17. The fix includes using new entity objects without merging them, which affects your test ... am wrong, i have just launched your test case with 2.4.5 version ( so before the fix ). Test
1

ObjectDB 2.5.2

Framework versions (with JPA 1.0). Fixed "InternalException: InterruptedException" due to application interrupts in embedded mode. Fixed a class loading conflict with Log4j. Fixed very slow processing of a composite BETWEEN query. Fixed NullPointerException when using AND TRUE in WHERE clause (issue
1

Removed entities can be found by query in the same transaction

.4_04. btc_es BTC EmbeddedSystems Build 2.7.4_04 fixes issue #2280 but seems to cause new issues ... other transactions after that flush were not visible to that transaction (until commit). Build 2.7.4_04 fixed ... that the fix in build 2.7.4_04, which improves visibility of committed changes in other transactions
1

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

an internal ObjectDB error, which is not specifically related to MEMBER OF query. A similar issue was fixed ... with the Doctor. If the error repeats, try to fix the database by running the Doctor in repair mode ... to understand and fix the issue without this help. Build 2.6.3_04 should fix it. The issue is caused
1

ObjectDB 2.5.5

that is already running (avoiding further attempts). Fixed a memory issue with using ObjectDB with JBoss. Fixed query execution issues with using composite indexes. Fixed a bug in using LIKE operator in some combinations of different wildcards. Fixed a bug in handling dates (TemporalType.DATE) on some
1

ObjectDB 2.7.5

). Fixed a bug in restricting server access to a range of IPs (issue #2292). Fixed a bug in comparing array fields against parameters in queries (issue #2289). Fixed a bug in retrieving new objects of other transactions after flush (issue #2280). Fixed a bug in version 2.7.4 in automatic primary key
1

ObjectDB 2.6.8

of pessimistic locks on client-server connection failure. Fixed an OptimisticLockException bug on commit after flushing a removed modified entity object. Fixed a NullPointerExeption on new index building. Fixed a NullPointerExeption on flush (issue #1840). Fixed a bug in using temporary files in large
1

ObjectDB 2.0.5

Fixed Java Agent / Java EE / Spring enhancement bug. Fixed a bug in merging detached entity objects. Fixed unexpected NullPointerException in client server mode. Fixed an exception in AVG query on non numeric values (issue #107). Fixed a bug in handling JOIN queries with primary key fields.
1

Negative snapshot user count exception

may be relevant: Your move from ObjectDB 2.3.x to 2.5.2. Corruption of the database that cannot be fixed by ... . Rolling back to 2.3.x would be a problem because development work I did this year relies on fixes ... , but they are not seen in the log after that restart, so hopefully the Doctor fixed these index issues. In

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