About field

forum_thread

Speed of queries that return many objects

Hi, I have a DB of 146MB - with 1_000_000 elements. Loading the contents (objectDB query in java) takes about 10sec. I am using a recent MacBook (SSD blabla - disk I/O speed is about 400MB/sec - according to blackMagicTest app for mac) - so I was expecting the query to take less than one sec (146/400 = 0.35sec.. + some overhead). I was wondering if this kind of speed is "normal", or if this is something I should investigate. Thanks EKK #1 2015-08-29 21:10 Hi, I have a DB of 146MB - with 1_000_000 elements. Loading the contents (objectDB query in java) ...

 
issue

ArrayIndexOutOfBounds on showing Tree Window

... from the Schema in ObjectDB Explorer in version 2.6.5_04 I get then the following exception (plenty of them). ... indicates a bug in handling the rare situation in which a field is included in the summary view but excluded from the main (table/tree) ...

 
issue

Sort of very large objects - out of memory

The attached test is failing with an out of memory exception when running with -Xmx512m It performs the following actions: 1) Create 5 persist threads which create and persist a large object in a loop 100 times each 2) Create 5 get threads which read 100 objects each in a loop based on object creation time and priority The message size should be around 1mb so I think there should be around 11mb of "live" data in play at any time. The objectdb cache settings are low in the config - database section is below for reference. Feature Request Version: 2.3.0 Priority: Normal Status: Active Replies: 2 Type:  Feature Request ...

 
forum_thread

LEFT JOIN FETCH over empty embedded collection returns no results

First of all, thank you for promptly implementing JOIN FETCH over nested paths in response to my inquiry a few months ago. However, I have run into one problem: if an embedded collection is empty, but I attempt to LEFT JOIN FETCH all the members of a collection within a (non-existent) member of the first collection, the result of the overall query is an empty set. To use the example from my original post: @Embeddable class A { String val; };   ... :id; since B instances do not include a val field (there is also an invalid ; symbol at the end of the query). ...

 
issue

Query Execution Error

This query Bug Version: 2.3.6 Priority: Normal Status: Fixed Replies: 4 Type:  Bug ...

 
forum_thread

How to package orm.xml when using EJB in WAR?

Hi, I have database utility classes in one project, the id's use sequences declared in an orm.xml file for example: ... null value in non optional field unitId (error 648) which seems to imply that the sequence ...

 
forum_thread

Problem of Enhancer with JAXB / Proxified Entity Bean.

Hello Support, I run on a prod server an objectdb java agent with my app. In this application, all my entities beans are constructed from a JAXBContext ( SOAP CXF Webservice or Direct JAXB Unmarshalling ) When i watch the objectdb log, i see pages of errors. #1 2014-05-20 15:45 Hello Support, I run on a prod server an objectdb java agent with my app. In this application, al ...

 
forum_thread

Exception after update of indices of Entity class

Hello, I changed the index definition of an entity class from @Index()... to @Indices() and now I get the following stacktrace upon start: #1 2017-08-03 13:18 Hello, I changed the index definition of an entity class from @Index()... to @Indices() and now I get the ...

 
forum_thread

Clarification on free license restrictions

Hello,   My apologies if the answer is already on the website, but I’m struggling to find a definitive answer.  The 10 entity class restriction is very clear, but can each of these classes use unrestricted numbers of embeddable classes?  Do embeddable classes count as part of the ten?  I assume not, but I need to check before I code further (and learn more about the product).   ... an instance of a non persistable type tutorial.Person - field tutorial.Patient.person Thanks, Craig ...

 
issue

ClassCastException after upgrade to 2.3.5_03

On upgrading to the latest version of objectdb I get the following exception on object retrieval: ... ;   ... In this case the "payload" field is a byte[]. This worked ok in 2.3.3_06. ...