About Explorer

forum_thread

NOT NULL not working

I added a OneToOne Realtionship to one of my entity classes. To  give this field a value in my existing datasets i wrote an upgrade method. The cool thing is that SELECT u FROM Unit u WHERE u.lastPosition IS NOT NULL returns no datasets. Is this a bug or am i missing something? ... - given a test database the query can be checked in the Explorer)? ObjectDB Support ObjectDB - Fast ...

 
forum_thread

OrphanRemoval not working?

Dear all, I have entities Invoice and InvoiceItem, their relation is defined: public class Invoice implements Serializable { ..     @OneToMany(mappedBy = "invoice", fetch= FetchType.EAGER, orphanRemoval=true, cascade= CascadeType.ALL)     private List<InvoiceItem> invoiceItemList; .. } ... invoiceitem from the list removes it from db, but using explorer, I can see, that the entity is still there with invoice field setted ...

 
tutorial

Step 4: Add a Servlet Class

Explains how to add a servlet that manages persistence using JPA and ObjectDB to an Eclipse Web Application.... by right clicking the guest package node (in the [Package Explorer] window), selecting  New > Other... > Web > ...

 
manual

ObjectDB 2.6 Developer's Guide

... and Utilities Presents ObjectDB Tools: the Explorer, the Enhancer, the Doctor, etc. Chapter 6 - Configuration ...

 
forum_thread

Object comparation never matches

Hi! I'm trying to compare 2 identical objects in SELECT with no success: @Embeddable public class PhoneNumber implements Serializable {     int countryCode;     long number;   Which is a part of Customer object: ... ( ) ; According to ObjectDB explorer, the record is stored as expected. ... principal | PhoneNumber ...

 
forum_thread

Query vs Extent for retrieving data

I'm running into a problem where data that is retrieved via a Query comes out null, but when I retrieve it using an Extent everything is present. We have a very simple class: public class PositionReportManagerBean implements InstanceCallbacks { private int maxReports; private List<PositionReportBean> reports; } I have a test file with 5 instances of PositionReportManagerBean, each with maxReports set to 10 and 5 PositionReportBeans in reports. I can verify with the ObjectDB explorer that all of the data is there. If I call ... in reports. I can verify with the ObjectDB explorer that all of the data is there. If I call ...

 
forum_thread

ClassCastException of same object type

I have ObjectDB partially working with my project. At the moment it seems to be saving objects and retrieving objects ok in the main project. However, when I make a plugin for the project, the new objects are persisted but not retrieved. I get the following error: java.lang.ClassCastException: org.sportscoring.ssv.xc.core.XCCompetitorCount cannot be cast to org.sportscoring.ssv.xc.core.XCCompetitorCount ... an ICoreObject, not as a XCCompetitorCount. Yet using the Explorer I can see it in the db as a XCCompetitorCount. I would ...

 
forum_thread

Error 363 - Failed to read value of inverse relationship

I've got two objects: @Entity public class EEvent { @Id @GeneratedValue(strategy = GenerationType.AUTO) private long id; @ManyToOne(optional=false) private ETown town; public ETown getTown() { return town; } public void setTown(ETown town) { this.town = town; } } And: ... forward and inverse) behave as expected in the Object DB Explorer, however when I try to read the Event type, I'm getting the ...

 
forum_thread

Puzzler: Not getting cascades on read from Spring context

I've determined that the database is correctly initialized, looking at it from the Object Explorer, I can run the code that loads the database in a Junit test and it's initializing the children objects correctly, but in the application running in Jetty with Spring, fetching is not cascading. My best guess is that perhaps I have something misconfigured in my persistence.xml or my context.    -dh ... is correctly initialized, looking at it from the Object Explorer, I can run the code that loads the database in a Junit test and ...

 
forum_thread

Remove a modified entity cause an optimistic lock exception

Hello, the following examples load and modify an entity, and load and remove the same entity. The first example 'SetAndRemoveIssue.java' is a simple java program which executes without errors. The second example is an OSGi program which fails with an optimistic lock exception. Both examples are equivalent, please execute SetAndRemoveIssue.java (in the OSGi example as a plugin-test). Can you explain the optimistic lock exception? #1 2015-11-09 07:46 Hello, the following examples load and modify an entity, and load and remove the same entity. The ...