ObjectDB Database Search

The drop parameter  indicates a request to discard an old database (if exists) and create a new empty

to retrieve them or starting a new empty database every request - more details are needed. To view

.Skill.Campaign.Id=: campid And agsk.Skill.Queue.Channel=:chan" for this query am getting empty result

unlimited debugging services. Please understand that it doesn't matter for ObjectDB if you store an empty

without entity classes in the classpath but the metamodel is empty . How does your explorer get to metamodel

the cost of these operations, and mainly the addressSet retrieval when the database is not empty

Hi! I started to use ObjectDB Explorer to administrate a remote DB (on a server), but it seems to be very slow. The database is quite empty now, just between 5-20 records / entity, but it's still very very slow. That's the only thing that is slow on my server... How can I speed it up? zmirc Mircea

should mention that I have tried running NetBeans in admin mode, and I have tried creating an empty "punkter

} Maybe you have an existing database in that path, which contains a Person#1 instance with an empty

with an empty database: import java.util.*; import javax.persistence.*; public final class T1009 {   

might look empty - but as soon as your application accesses its content (e.g. by invocation of the size

Hi all, I want to get objects with their lists, even when the lists are empty . So I've witten this query: "SELECT i FROM Invoice i LEFT OUTER JOIN i.itemList items" But this query never returns invoices without items! Only invoices with items. When I remove mappedBy from @OneToMany annotation

I'm trying to persist an Entity containing a HashMap. It stores the data in the database OK, but the map is always empty when I get the entity out of the database again. I've reproduced this problem in a simple variation of the Guestbook tutorial: Guest class: ===================== @Entity public

Feature api of SubstrateVM, I could see the paramString and size of paramArrayOfByte is not empty

Suppose I have two entities... A B - A B has a ManyToOne relationship with A. When my database is empty and I persist a valid B entity (that contains actual A reference) I observe some behavior that I'm not sure I understand. 1. In ObjectDB explorer I see Both B and A Entity classes available in

lastInstanceInMap; protected Container() { // Empty constructor for JPA } public void generateMapItems

Hi, I am using objectdb.jar version 2.6.8 (installed via Maven). I am trying to authenticate a user. Initially, the database is empty . I have the following query: @javax.persistence.NamedQuery( name = "getPersonByName", query = "SELECT _person FROM metamodel.user.Person as _person WHERE _person

again. Without activation codes it should show different results. Please try also opening an empty database in

", "startTime", "channelNumber"}) Start with a new empty database, in order to make sure that the new

applying the attribute List jrchalaco Roberto Pinto Both databases in #5 above seem to be empty

. rumblesnort Richard A new build, 2.5.3_02, adds empty implementation of the new JPA 2.1 methods. We haven't

the Vector dissapears and I get an empty vector. Something weird happens, if BEFORE closing

entity is created, the table is empty , however categories are well present within Product (as

(MyEnumType.VALUE1, MyEnumType.VALUE2)); Then query.getResultSet() *always* returns an empty list

any issue. Could you please try your conversion program with a new empty log file and then search

in lower logging level (e.g. info ). The empty database might be the result of another issue

the relationshipType index back and started a test with an empty database. It slowed down significantly

()); //DB is empty em.getTransaction().begin(); em.persist(entry); em.getTransaction().commit

the existence of a special empty file (a file whose name is active  in the odr directory). If this file

that the attachments field is still empty ). You find a complete use case at http://www.objectdb.com/database

Added support for integration with WebSphere / Liberty application server. Fixed deletin g large transaction temporary files (in the experimental large transactions feature ). Fixed empty log directory creation when logging is disabled. Fixed a bug in using nested embedded objects. Fixed a query

relationship constraints/constrainedElements test fails on test case, appears empty  (www.objectdb.com

\.plugins\org.eclipse.birt.report.data.oda.jdbc.dbprofile.sampledb\db\ is empty ... Log dump: eclipse

in an empty temp directory, scan the backup directory for a newly created backup database-file (in

Using @Index for fields and filter more than one field with "and" predicate ends in empty result list. public class IndexTest {     @Entity     @Indices({         @Index(members = {"children.name"}),    

When a new index is added to an existing entity classes that already has instances in the database, it cannot be used in queries, because it starts empty and unsynchronized with the existing primary data. The Index Rebuilder tool will enable rebuilding indexes, synchronizing their data