About report

forum_thread

Unable to execute update query

Hello! I'm trying to do an update query via the explorer to set a new field value for around 400k objects. UPDATE Position p SET p.originalData = null This exception raises when I try to do it: ... query, but the cause is unclear, and according to your report that specific temporary file exists. Can you reproduce the ...

 
forum_thread

lockfiles in client/server mode

i have an objectdb server running on localhost as user "objectdb", spawned like so: java -server -cp /usr/local/share/objectdb/objectdb.jar: com.objectdb.Server -conf /etc/objectdb/objectdb.conf start it has naturally created and taken ownership of /tmp/ObjectDB. ... should be avoided now. Thank you for this report. ObjectDB Support ObjectDB - Fast Object ...

 
forum_thread

Double persist of Entity field with Cascade.ALL

I am building a JavaEE application using Netbeans 7.0.1, Glassfish 3.1 and ObjectDB 2.3.3. I have a Book class with entity field Chapter which has a CascadeType.ALL property. The Book fields are as follows: @Id @GeneratedValue(strategy = GenerationType.AUTO) private Long id; private String bookTitle; @OneToMany(cascade= CascadeType.ALL, fetch= FetchType.EAGER) private List<Chapter> chapters; The Chapter fields are as follows: ... it will be fixed soon. Thank you for this report. ObjectDB Support ObjectDB - Fast Object ...

 
release

2.7.0

... Version 2.2.7 Added support of report generation using BIRT . Fixed a bug in query optimization ...

 
issue

InternalException during producer/consumer scenario

Hi, I'm trying to use objectdb in a producer/consumer scenario. Producer threads put message objects into a table while consumer threads remove the objects based on age, priority, etc. There are 2 main motivations for using objectdb for this purpose rather than a queue or similar data structure: 1) The consumer can select the "next" object based on a range of potentially complex criteria. 2) The number of objects produced can be potentially exceed available memory so can be held on disk within the objectdb file. ... Version 2.2.1 fixes these problems. Thank you for this report. ObjectDB Support ObjectDB - Fast Object ...

 
release

2.6.9

... Version 2.2.7 Added support of report generation using BIRT . Fixed a bug in query optimization ...

 
forum_thread

Extra uninitialised entities spawned on merge()

In the following, Element is a base entity class, with a bi-directional @ManyToOne-@OneToMany relationship Element owner - List<Element> ownedElements, and Example is a subclass entity with a relationship @OneToOne Element child. ... Thank you for this bug report. Build 2.4.0_05 fixes it. You have to set the name field as ...

 
release

2.6.8

... Version 2.2.7 Added support of report generation using BIRT . Fixed a bug in query optimization ...

 
forum_thread

Activated ObjectDB still throws "Too many persistable types"

I have upgraded from 2.3.7 to 2.4.4 and now my activation won't work, throwing the dreaded com.objectdb.o.UserException: Too many persistable types (>10) - exceeds evaluation limit I have already reactivated and checked that my objectdb.conf is correctly used (by inserting random chars at the beginning of the file, which lead to an error). Yet I still get the error thrown. Nothing in my configuration changed except the version. What could possibly be the problem with that? ... You are welcome. Thank you for this report. ObjectDB Support ObjectDB - Fast Object ...

 
forum_thread

Upgrade to 2.4.1_01

Hi, We tried to upgrade from 2.3.7_18 to 2.4.1_01 to pickup some fixes. We discovered that our code no longer works when using 2.4.1_01. We did some probing and found one thing. I have attached the unit test to display this issue. The problem seems to be the annotation at line 266 in the test. In our code for 2.3.7_18, we had @OneToOne(cascade=CascadeType.ALL, fetch=FetchType.EAGER), which is wrong, as Contactdetails is Embeddable, the annotation should be @Embedded. Neither annotation works with 2.4.1_01, with each giving a different error. ... Thank you for this report and for isolating the problem with a test case. Please try build ...