ObjectDB ObjectDB

Internal Website Search

61-70 of 200 resultsRefresh
16

Inserted entities with strings as keys and indices needs more and more ram memory in comparing to primitive integers as keys and indices

programs demonstrate well that automatic long primary keys are indeed much more efficient than String ... to the maximum with new objects. Long values consume less space than String UID and are processed faster. support Support Thank you for the clarification. The example with long keys needs round about 750 MB
16

Optimistic locking: prevent version increment on entity collection attribute

@Entity public class Document {        // ID is generated by the database     @Id private long id ... <Reading>();        public long getId() {         return id;     }        public ArrayList<Reading ... is generated by the database     @Id private long id;     private Document document = null
16

Composite Index error 328

UsrlistEntity implements Serializable { private static final long serialVersionUID = -4472890635861972890L; private int id; private int dyId; private long pwd; private String ... job; private String phoneNumber; private Long contactHash; private String kadrosu
15

ClassCastException on SELECT NEW ... after UPDATE over Java RMI

Long id; private String fileName; public FileNameDTO(Long id, String fileName) { this.id = id; this.fileName = fileName; } public Long getId() { return id; } public void setId(Long id) { this.id = id; } public String
13

Need help to make this test work and define proper annotations for entities Lists

class OrderDat implements Serializable {             @Id @GeneratedValue private long id ... ;                 this.items = items;             }             public long getId() {                 return id;             }             public void setId(long id) {                 this.id = id
3

javax.persistence.MapsId

has simple primary key @Entity public class Employee { @Id long empId; String name ... public class DependentId { String name; long empid; // corresponds to primary key
0

nextValue()

Method javax.jdo.datastore.Sequence long nextValue() Returns the next sequence value as a long. If the next sequence value is not available or is not numeric, throw JDODataStoreException. Returns: the next value Since: JDO 2.0
0

currentValue()

Method javax.jdo.datastore.Sequence long currentValue() Returns the current sequence value as a long. If the current sequence value is not available or is not numeric, throw JDODataStoreException. Returns: the current value Since: JDO 2.0
0

getLongField(pc, field, currentValue)

Method javax.jdo.spi.StateManager long getLongField( PersistenceCapable pc, int field, long currentValue ) Return the value for the field. Parameters: pc - the calling PersistenceCapable instance field - the field number currentValue - the current value of the field Returns: the new value for the field Since: JDO 1.0
0

setLongField(pc, field, currentValue, newValue)

Method javax.jdo.spi.StateManager void setLongField( PersistenceCapable pc, int field, long currentValue, long newValue ) Mark the field as modified by the user. Parameters: pc - the calling PersistenceCapable instance field - the field number currentValue - the current value of the field newValue - the proposed new value of the field Since: JDO 1.0

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support