About remove


Login Error (bad username 'admin' or password)

I am getting following error when i am trying to connect to server: [com.objectdb.o._PersistenceException: Login Error (bad username 'admin' or password)] with root cause com.objectdb.o.UserException: Login Error (bad username 'admin' or password) at com.objectdb.o.MSG.d(MSG.java:61) at com.objectdb.o.HND.K(HND.java:210) at com.objectdb.o.SHN.K(SHN.java:208) at com.objectdb.o.HND.run(HND.java:132) at java.lang.Thread.run(Thread.java:662) Here is my connection string: ... and the client side. In addition, you should remove blanks from the connection url. ObjectDB ...


Database Schema Evolution

Explains how ObjectDB handles automatically schema changes. Modifications to entity classes that do not change their persistent field definitions (their schema) are transparent to ObjectDB. This includes adding, removing and modifying constructors, methods and non persistent fields. However, additions, deleti ...


exceeds evaluation limit Exception

Hi ,every body i have this exception , and i didn't know what is mean or from "Exception in thread "main" [ObjectDB 2.0.5_02] javax.persistence.PersistenceException Too many persistable types (>10) - exceeds evaluation limit (error 1011) at com.objectdb.jpa.EMImpl.persist(EMImpl.java:357) at DBManager.insertPatient(DBManager.java:29) at Main.main(Main.java:374)" does any body face this exception before Thanks in Advance     ... Larger companies are required to purchase a license to remove this restrictions. Anyway, you need a license key to remove this restriction. ObjectDB Support ...


Internal Exception and Index Problems

Dear Support Team, we have an urgent issue in a productive database. The objectdb doctor finds no error but one string field of one database item is not editable (even not using the objectdb explorer). The corrupt entry is in entity "UserModelData" with id="7d29d5eb-69a6-4d46-9bf1-802cbb6e439b". Try to change the userName attribute of this entry then the following error occurs: Bug Version: 2.5.3 Priority: High Status: Active Replies: 8 Type:  Bug ...


String comparison in query where clause

I am having trouble getting a simple string comparison to work in an SQL "where" clause.  It is my understanding that queries are case sensitive by default and I do not want that, so I am constructing the query as follows... SELECT e FROM Exercise AS e WHERE UPPER(e.name) = ?0 and then I am converting the parameter (representing by position ?0) to upper case.  I am certain the parameter value is correct, and there should be a matching record in the database, but my query returns no result. ... issue or question.  I would like to just remove the thread from the forum complete.  Can you do that? ... it would be better to close this thread now but not to remove it (at least yet). ObjectDB Support ...


Foreign key constraint issue

Hi, I'm trying to create two tables (Parent and Child) with a foreign key constraint from Child to Parent so that when the parent is deleted all children are removed as well. Unfortunately, in one specific case that foreign key constraint doesn't apply and I can't figure out what I'm missing. The definitions of the classes are as follows: ... @OneToMany(cascade = {CascadeType.MERGE, CascadeType.REMOVE}, mappedBy = "parent", orphanRemoval = true)     ... the parent's list get deleted, whereas I'd want to remove all orphaned child entities (as with a foreign key constraint). ...


collection of embedded objects

1. In general, are there any restrictions of the use of @Embedded objects in collections, compared to @Entity? 2. If you have a large nested collection of @Embedded objects, and you remove the parent @Entity, does the remove cascade through the whole collection? 3. Is searching through collections of @Embedded objects more expensive (time) than searching through collections of @Entity? ... large nested collection of @Embedded objects, and you remove the parent @Entity , does the remove cascade through the whole collection? 3. Is searching through ...



com.objectdb.o.InternalException: java.lang.UnsupportedOperationException: Unsupported feature - Update queries are not supported yet java.lang.UnsupportedOperationException: Unsupported feature - Update queries are not supported yet. Used with this code: "DELETE l FROM License l WHERE l.id = ?1", License.class); query.setParameter(1, id); int changes = query.executeUpdate(); Is there a workaround? ... The obvious workaround is to use remove : List results = query. getResultList ( ) ... ( Object entity : results ) em. remove ( entity ) ; em. getTransaction ( ) ...



Remove the members (fields or properties) of the named category from the set of members in this FetchGroup.(Method of javax.jdo.FetchGroup)



Remove the specified key and its value from the map of user objects.(Method of javax.jdo.PersistenceManager)