ObjectDB ObjectDB

Internal Website Search

191-200 of 200 resultsRefresh

Annotate a Map field with @ElementCollection or @Basic

. It could be due to the different default fetch value (LAZY for ElementCollection, EAGER for Basic). You may try using an @ElementCollection(fetch=FetchType.EAGER) and see if it is fast as @Basic support Support I tested it already with @ElementCollection(fetch=FetchType.EAGER). It is little bit faster as before

Entity with java.util.Date column gives ClassCastException in BIRT

.eclipse.birt.data.engine.odaconsumer.ResultSet.fetch(ResultSet.java:189) at org.eclipse.birt.data.engine.executor.cache.OdiAdapter.fetch(OdiAdapter.java:214) at org.eclipse.birt.data.engine.executor.cache.RowResultSet.fetch(RowResultSet.java:145) at org.eclipse.birt.data.engine.executor.cache

Puzzler: Not getting cascades on read from Spring context

objects correctly, but in the application running in Jetty with Spring, fetching is not cascading ... dhosek Don Hosek Fetching doesn't work by default for detached objects. Please read see this issue ... Hosek It would be better and more efficient, if possible, to arrange fetching of the relevant data before detachment. support Support

Multi threading on DMOs by lazy loading

It is possible to use lazy loading on fields of attached entities by several threads? Example: class EntityZ { @OneToOne(fetch = FetchType.LAZY) EntityX fieldX; @OneToOne(fetch = FetchType.LAZY) EntityY fieldY; @ElementCollection (fetch = FetchType.LAZY) List

Cast exception?

cannot be cast to database.entity.Player From just fetching a single result: TypedQuery<Player> query = em ... :615) java.lang.Thread.run(Thread.java:722) So basically the query fetched the persistent fields ... testing revealed that there is no error on the fetching request. I could have written: Object player

List of Enum Values in an entity

the problem is to change the fetch policy of the field from LAZY to EAGER:     private @OneToMany(fetch ... this error / warning try: private @Basic(fetch=FetchType.EAGER) List<GuestFlag> flags; support Support

Changes in detach behaviour?

The last builds include fixes for some fetch issues so it is possible that ObjectDB behaves differently now ... automatically. Loading of collections may require setting EAGER fetch explicitly ... version 2.3.4 then the output is "username". I think lazy fetching of primitive fields is a bit

Broken @ManyToOne reference

: @MappedSuperclass public abstract class A { @Id @ManyToOne(fetch = FetchType.EAGER, cascade=CascadeType ... This is an unexpected behavior, B instances should be fetched eagerly in this case. Please follow the posting ... (fetch = FetchType.EAGER)   public AbstractParent prn; } the output of the tests seems as expected

TreeSet and compareTo() issue

fetch: @OneToMany(fetch = FetchType.EAGER) private Set<DropdownValue> dropdownValues = new ... persist should be added to make the test valid:     @OneToMany(fetch = FetchType.EAGER, cascade


CacheableJobStat { @OneToOne(fetch = FetchType.EAGER) private CacheableJobInfo ji; @OneToOne(fetch ... , but explicitly by calling persist. The problem dissapeared when removing the @OneToOne(fetch = FetchType

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