ObjectDB Database Search
101-147 of 147 resultsBeginners questions "RESULT" due to class annotation @Entity(name="RESULT"). 2.1. Why? Is the @Entity(name="RESULT") ignored by ObjectDB? 2.2. Is the annotation @Entity(name="RESULT") relevant for ObjectDB in any | |
Date field Index is corrupted due to time change; import javax.jdo. annotations .Index; import javax.jdo. annotations .Indices; import javax.persistence | |
Indexing a field results in internal Exception the @Index annotation to the field I eventually end up with an ObjectDB internal exception.   ... annotation . Is there anything I can look for that might result in this exception? sjzlondon Steve Zara | |
Cascading delete Is there a configuration parameter to set this? dmoshal David Moshal You can set cascade delete using annotations (see also the Orphan Removal section). JDO defines similar annotations , and both JPA and JDO support this setting also in XML files, but no additional parameters exist in ObjectDB | |
failure to enforce NOT NULL for java.lang.String my test cases are indicating that @Basic(optional=false) and @Persistent(nullValue=NullValue.EXCEPTION) are not enforced in 2.3.7_08 or that i have failed to understand how to annotate . example ... ): import javax.jdo. annotations .*; import javax.persistence.*; public class T744 {   | |
openejb jpa jaas module Templates. } } package com.bayner.jpa; import network.data.Settings; import javax.jdo. annotations ... = principals; } } package com.bayner.jpa; import javax.jdo. annotations .Index; import javax.persistence | |
Broken @ManyToOne reference described in #1. It is unclear why is the @Id annotation used in more than one level in the child hierarchy. This is invalid in JPA and it is not supported by ObjectDB. After commenting the @Id annotation | |
mapping file is not being loaded JDBC connection. The entity classes use no JPA annotations , as some of our internal | |
Is there a way to set EAGER fetch on all "ToMany" collection relationships Given that the default seems to be FetchType.LAZY for all collections @OneToMany and @ManyToMany. Such as a configuration option. Instead of having to explicitly set fetch in annotation code in every relationship. webel Dr Darren Kelly No. There is no such configuration option, since having EAGER | |
Problem on JPA Merge Entity. @Transactional annotation on ErgoDaoJpa ? Check entityManager.getTransaction().isActive() - in | |
LifeCycle Event with Embeddable classes and prepersist annotation are a quite elegant way of setting these properties. ObjectArts   | |
Duplicate Entity class names causes Exception in Query console test apps! Thanks for your help. BTW the @Unique annotations for non @id attributes makes | |
ObjectDB throws `NullPointerException` in internal code (`com.objectdb.o.ENH.b`) that was missing the @Entity annotation by mistake) to a valid entity class, though this is not entirely | |
Optimistic locking: prevent version increment on entity collection attribute is annotated with @Transaction for that purpose) so not sure how Documents found by query in | |
@Column length is not working. and objectdb file. Deepak_1996 Deepak Kumar Maharana ORM annotations , including @Column are   | |
Problem persisting a TreeSet field an automatic query . You can define the field as List and use the @OrderBy annotation to refine | |
How to Use a SF with extended Persistence Context? the annotations @TransactionManagement and @TransactionAttribute but I guess I failed since I got | |
StackOverflowError after commit, some of our Entity classes were annotated with @Embeddable instead of @Entity the objectdb error | |
Intermittent: "Attempt to reuse an existing primary key value" when persisting a new instance using the following annotations for the id: @Id @GeneratedValue(strategy | |
Index on map key javax.jdo. annotations .Index; import javax.persistence.*; public class T1255 { public | |
Unique contraint with 2 members constraint" exception: import javax.jdo. annotations .*; import javax.persistence.*; public class T486 {   | |
Upgrade to 2.4.1_03 Right, that fix to 2.4.1_02 got us past the previous issue. Now I'm not sure whether this next issue is our annotations , or another issue with objectdb. I have added some more classes to the unit test. They are used by AbstractContactDetail. On line 372 of the attached test, AbstractContactDetail | |
Executing JUnit "all tests" throws "Object ... belongs to another EntityManager" Exception , which suggests (to me) that I'm not controlling the Symbol class adequately. ( @PersistenceCapable annotates | |
Does ObjectDB support lazy loading?. The EntityManager is not yet closed when the getters are called. After I change the annotation | |
Adding indexes on existing entities. index definition (either annotation in class or xml), or run the Doctor with this available in | |
Join performance in Objectdb the problem. Maybe the id fields in Page and Image are not annotated with @Id or @Index . In that case | |
newbie - lots of exeptions is thrown when ObjectDB tries to scan classes in order to find entity classes and other annotations | |
@PrePersist Problem HI I am trying to use @PrePersist annotation in my project.This application is using struts2 with jpa combination .so can u please tell me how to us this annotaton before save the record into persistence. claerly how to use in pojo and in action class rameshanem rameshanem Please read this manual page . support Support | |
Optimistic Locking com.objectdb.example; import java.util.*; import javax.jdo.*; import javax.jdo. annotations .*; public | |
Performance issue in a query due to compareTo calls TCStep step; btc_es BTC EmbeddedSystems @javax.jdo. annotations .Index | |
disabling JDO in objectdb embedded mode external XML files in addition to annotations . Therefore, ObjectDB must check if such XML files exist | |
Failed to enhance dynamic type for analysis ( annotation extraction, serialversionUID calculation, etc.). Class loading fails (by the JVM | |
Internal exception when updating date filed (TemporalType.DATE).util.*; import javax.jdo. annotations .Index; import javax.persistence.*; public class T1312 {   | |
How to package orm.xml when using EJB in WAR? annotated with @Startup can access the database OK for both read and write, suggesting that the orm.xml | |
Standalone server needs dependencies? it working, I had to move the @Id annotation from the getter getUserId() to the field userId.  | |
UserException: Package com.example.model is not found by the enhancer annotation this can be achieved? ThreaT Ashton Hogan Enhancement using an invocation of Enhancer | |
Error in reading Enum in JPA - Failed to read using reflection. It should be ordinary enum with no annotations (such as @Entity ). If you cannot see anything wrong | |
"is not null" queries not working with index "is not null"-queries are not working correctly for indexed fields. Following SSCCE creates 1000 entities. A null value is assigned to an indexed field for every second entity. When doing count-queries at the end, wrong results are fetched. import java.io.Serializable; import javax.jdo. annotations | |
Unlimited JPA Persistable Types I think it would be revolutionary if it were possible to persist any Java object, not just the standard SQL-based objects. Perhaps introducing an annotation will allow for this, something like @BasicType. The ability to store the state of an entire application would be a new innovative approach | |
NullPointerException in __odbGetNumMember field version using enhanced method version is annotated with @Version quasado Alexander Adam Okay | |
auto-generated uuid fields/api/java/jdo/ annotations /IdGeneratorStrategy which lists the UUIDHEX and UUIDSTRING strategies | |
NullPointerException on initial database creation it may be related to having a class annotated with @Startup or @ApplicationScoped that references | |
ObjectDB enhancement fails on "is" form for @Transient boolean isLoaded(), ok for "getter" form @Transient boolean getLoaded() that annotations on "is" methods of boolean persistent JavaBean properties have been ignored | |
Unexpected exception (Error 990) - NullPointerException writing an interceptor annotation that logs all exceptions. Without this interceptor the log file | |
I can't get cascading delete to work in JDO.Query; import javax.jdo. annotations .*; public class F2329 { public static void main | |
Feature suggestion: auto-detection of entities via persistence.xml extension-file in the persistence.xml file (but not the entire classpath) are searched for annotated | |
NullPointerException when using multithreading() on the database. To my knowledge the entity and embedded classes are annotated correctly.  |