Home » Search

About tracking

71-80 of 120Refresh
Forum
1

JPA Query language support in OBjectDB / Sub query or nested Query

are not supported yet. The issue tracking system contains an up to date list of unsupported JPA features. Sandeep
Issue
1

Lazy loading of mapped by (inverse) singular references

object with inverse fields tracking which inverse fields have been loaded and references
Forum
1

locks on pure query activities

-tracking arrays="true" />
Forum
1

Maintaining referential integrity

to this new feature request if you need this functionality. Please add your comments regarding this feature (if any) in the issue tracking system. franz
Forum
1

Memory consumption of empty Strings

improvement. The other enhancement was added as a feature request to the issue tracking
Forum
1

Memory leak while merging parent with No Cascade annotation with children

Hello support, While tracking memory leak in my application i suspected a memory leak in the merging object db implementation. The test case is the following, just run and watch the "Memory Used" by comparing Cascade.ALL (or Cascade.MERGE ) to nothing. Tested with last version of Object Db ( 2.5.5
Forum
1

Merge Issue: Attempt to reuse an existing primary key value

on 3 B items ) and so we may discuss more about this behaviour :) It is difficult to track all the old
Forum
1

migration path from JPA / Hibernate

features are not supported yet by ObjectDB (but expected to be supported soon). See the issue tracking
Forum
1

Modifying something with Explorer -> app JPQL with Enum doesn't work anymore

issue tracking route. Thank you for your understanding. Maybe you can even demonstrate the issue
Issue
1

New Java 8 (JDK 1.8) Collection Methods

ObjectDB version 2.5.5 (and above) supports Java 8 (JDK 1.8). Tracking changes to collections and maps using some new Java 8 methods is currently not fully supported. The main known issue is that orphan removal does not happen as a result of removing a reference to an object