ObjectDB Database Search

Hi, Given : @Entity(name = "Inspiration") public class Inspiration implements Serializable {     ....     @ManyToOne(fetch = FetchType.EAGER)     protected Atelier atelier;     .... } I have a query : SELECT i FROM Inspiration i WHERE i

TestIdHolder implements Serializable {     private static final long serialVersionUID = 1L

up. My entity looks like this .. @Entity public class av_booking implements Serializable { @Id

In user model class I have the following: public class User implements Serializable {     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @ManyToMany(mappedBy = "attendees", cascade

Serializable { private static final long serialVersionUID = 1L; @Id public String nodePath; ... as soon as

We have a class with a one to many relationship declared like this (1 or more objects of the same class are linked into the relationship, no circular referencing): @Entity public class ObjectNode implements Serializable { private static final long serialVersionUID = 1L; @Id public String uUid

implements Serializable { @PrimaryKey private long id; private String name; protected TestClass() { } public

; @Entity public class Task implements Serializable { @Id @GeneratedValue int id; //int id = 0; private

value type java.io. Serializable for field org.springframework.data.jpa.domain.AbstractPersistable.id

. Caused by: com.objectdb.o.UserException: Unsupported auto value type java.io. Serializable for field

Hi, Is there a reason why we can't persist an object with a field of type EnumMap in ObjectDB? but it works fine for fields like = HashMap Thanks EKK EKK Emmanuel Keskes You can persist any Serializable type if you enable this ability in the configuration. But using this feature is not recommended

base class entity (except that it in turn inherits from a non-entity Serializable class that provides

In the docs, all serializable types should be persistable. However, when I tried to persist a field of type AtomicInteger, I got the following message: Message: Failed to commit transaction: Attempt to store an instance of a non persistable type java.util.concurrent.atomic.AtomicInteger I am using

", "ValidAttributes"}) public class Project implements Serializable {     @Id    

before). Here's my class: public class User implements Serializable { private Long id; private

implements Serializable {     @Id     private String id;   

): @Entity public class ObjectNode implements Serializable { private static final long serialVersionUID

abstract class Value implements Serializable , metamodel.IValue {   @javax.persistence.Id  

I don't think JDO supports altering an entity's Application Identity.  Does ObjectDB? @PersistenceCapable public class MyClass implements Serializable , Cloneable{ @Id private StringIdentity id; ... }   PersistenceManager persistenceManager = ...; Transaction transaction

Hello  !! I am new in JPA / ObjectDB development and I have many questions:   2. Object creation I created a class named EBResult which looks like this: @Entity(name="RESULT") public class EBResult extends Pojo implements Serializable {..... In ObjectDB-explorer (which is part of ObjectDB

AuEntity implements Serializable { @Id @GeneratedValue long id } it's the ONLY place in the entire

The beginning of my "Sample" class looks like: @Entity @SequenceGenerator(name = "sampleSeqGenerator", initialValue = 1, allocationSize = 100) public class Sample implements Serializable { private static final long serialVersionUID = 1L; private String sampleName; @GeneratedValue(strategy

I've got this class... @Entity @Table(name = "language") public class Language implements Serializable { ... private List aliases; ... public boolean hasAlias(List alai) { return ... ; } ... } When I try to make this JPQL query: SELECT g from Language g where g.hasAlias("espanol", "italian

I have a entity as bellow :- @Entity @Table(name = "agent") public class Agent implements Serializable { @Id @GeneratedValue(strategy = GenerationType.AUTO) private Long Id; private List SocialMedias; public Agent() { } public Long getId() { return Id; } public List getSocialMedias() { return

How to apply constraints like unique, not null ...etc in collection attribute of a entity. Example : @Entity @Table(name = "agent") public class Agent implements Serializable { @Id @GeneratedValue(strategy = GenerationType.AUTO) private Long Id; private List PhoneNumbers; public Agent() { } public

whether enhancement is required? My code: @Entity public class Boat implements Serializable { @Id private String name

implements Serializable { private String id; private String channel; .....   ENTITY: @Entity

implements Serializable { /** * */ private static final long serialVersionUID = 5019171545896480392L; @Id

Why can the field "contracts" be "null"? ---------- @Entity @Inheritance(strategy = InheritanceType. TABLE_PER_CLASS ) public class Person implements Serializable ,Subject {     @Id @GeneratedValue     private long id;     @ManyToMany(fetch = FetchType. EAGER , cascade

private LocalizedValues names; ... } @Embeddable public class LocalizedValues implements Serializable

. What could be the other reason it's still working for me? my entity class is Serializable though. I'm using

@Entity class WebReference implements Serializable {     private @Id    

The @Converter annotation and the Attribute Converter interface have two big benefits: 1) They make it possible to persist any as-yet-unsupported java types that do not implement java.io. Serializable . (If they do, it is possible to persist them automatically by turning on the   option in

On Page: http://www.objectdb.com/java/jpa/entity/types Under: Serializable Types "The internal Java serialization format will be inaccessible to future versions of ObjectDB on other platform." ...should be platforms (plural).   rwehrli Rob Wehrli Thanks. Following your report the text was fixed. support Support

(The classes all implement Serializable where necessary, via a common inherited logging service class

"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