11 | Updating Entities void updateItem(String item, boolean empty) { if(item != null) { setText(item ... , String>() { @Override protected void updateItem(String item, boolean empty) { if(item ... item, boolean empty) { if(item != null) { setText(item); setAlignment(Pos.CENTER |
9 | mapping file is not being loaded, the Metamodel is empty - none of the entities referenced in the mapping file are present in the Metamodel ... empty with ObjectDB Set<EntityType> managedEntities = emf.getMetaModel().getEntities(); I am certain ... still returns the empty set when 'getEntities()' is invoked. The prototype is running in a Tomcat |
8 | Possible issue with LAZY Loading part of the test? Or should it be empty? Pretty much I want a unit test that shows the locationlist coming back empty, and then someway of calling so that it comes back populated. I'm uncertain now ... ; } This method is used by ObjectDB to initialize the field with an empty lazy proxy collection |
8 | Selective merge/cascade of detatched entity, 1000, 100); Salesman emptied = redistributeTargets(salesmen); System.out.println("Salesman " + emptied + " now has targets:" + emptied.getCompanyTargets |
8 | "where in" query why this result returns an empty set? List<Prez> results; TypedQuery<Prez> prezs = em.createQuery ... was an exception rather than an empty result set. Version 2.3.2 fixes the exception - please try it. If you still get an empty set with the new version - try to modify the following test case (that works |
2 | javax.persistence.criteria.FetchParent that have been made from this type. Returns empty set if no fetch joins have been made from this type. Modifications |
2 | JPQL support for mapped by (inverse) collectionsAs discussed and demonstrated in this forum thread, collection operators and methods (IS EMPTY ... query = em.createQuery( // "SELECT a FROM A a WHERE a.list IS EMPTY ... EMPTY List<A> list1 = em.createQuery( "SELECT DISTINCT b.a FROM B b", A.class |
1 | Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct) via a querying @EJB gives many fields null (and not even empty, I mean truly null). In the following ... either empty or populated are served as null (!). The query is performed by an @EJB: @Stateless public class ... non-null, either as empty or correctly populated). This seems to imply that ObjectDB operation |
1 | Can't open replicated database this may be related to the initial empty state of the database. I inserted a few rows into the databases ... (therefore, with an almost empty database this is more likely to happen frequently). It is unclear ... the exception and skip the query as I'll know the database is empty but this would be a bit messy as |
1 | File lock exception on odb$ affected as the dbs were empty anyway but I'm a bit worried about data loss if & when this is not ... to open that empty database with its associated odb$ file? support Support It was repeatable ... file exists but it is empty. Build 2.3.7_09 should fix this issue. Thank you for this report |
