Internal Website Search

Hello, I would like to be able to read or refer to the ObjectDB manual (v2) on my Kindle. Unfortunately, I didn't find any option to download the manual , either as a .pdf (most convenient) or as ... ) Is there such an option I'm unaware of on your website or could you make the manual available for offline

Request for a new JDO manual , covering ODB 2. dmoshal David Moshal Please subscribe to the ObjectDB 2 JDO Manual issue. Because writing a new manual and then maintaining two similar manuals , one for JPA and the other for JDO requires massive work, this will be done only if there is a sufficient demand. support Support

//Code without manual maintenance of derived fields in @EmbeddedId classes... import javax

. Feedback We would appreciate any comment or suggestion regarding this manual . Please send your comments or questions to support@objectdb.com .

The best source for learning ObjectDB is the ObjectDB Manual , which contains all the necessary information for using ObjectDB. The only required background is a good understanding of the Java language. Reading the manual and getting started with ObjectDB could be easier for developers with prior

JPA defines three types of persistable classes which are set by the following annotations: Chapter 2 of the ObjectDB manual explains these annotations in detail. Entity and mapped super classes ... are useful in representing composite primary keys as explained in the Primary Key section of the ObjectDB manual .

online  Developer's Guide/ Manual . ObjectDB Manual in PDF format is included in ObjectDB

this manual can be replaced by equivalent XML in the mapping files (as explained below). The jar-file elements ... to annotations. Both JPA mapping files and JDO package.jdo files are supported. This manual focuses on using

), which is more Java oriented and is based on the syntax of Java. JDOQL is not covered in this manual (see chapter 7 in ObjectDB 1.0 manual for a description JDOQL).

The following annotations can mark methods as JPA callback methods: The Lifecycle Events section of the ObjectDB Manual explains how to use all these annotations on callback methods and with listener classes.

The following annotations are used to define static named JPA queries: The JPA Named Queries section of the ObjectDB Manual explains and demonstrates how to use these annotations to define named JPQL queries.

The way a field of a persistable class is managed by JPA can be set by the following annotations: Additional annotations (and enum) are designated for enum fields: Other additional annotations (and enum) are designated for date and calendar fields: Chapter 2 of the ObjectDB manual explains how to use all the above annotations.

of these documentation pages is to serve as a reference. In order to learn how to use JPA and ObjectDB please read the ObjectDB manual .

Queries are represented in JPA by the Query and TypedQuery interfaces: The JPA Query API section (in chapter 4 of the ObjectDB manual ) provides detailed explanation of how exactly to use these interfaces to build and run JPQL queries. The TypedQuery interface (or alternatively the older Query

and less so when using ObjectDB, this alternative is not covered in this manual . Using Named Queries

: More details about automatic value generation are provided at the Generated Value section of the ObjectDB Manual .

Mapping (ORM) tools can reduce some manual work but cannot eliminate the extra processing time

variables in the FROM clause: See the JPA Metamodel API page (in the ObjectDB manual ) for more details and examples.

This chapter introduced the basic principles of JPA using ObjectDB. You can go into details by reading the other chapters of this manual . If you prefer to get started with ObjectDB right away you can follow one of the following tutorials to create and run the example program that was described in

of this manual describes how to use JPA for database operations in more detail.

Welcome to ObjectDB for Java/JPA Developer's Guide. Here you can learn how to develop database applications using ObjectDB and JPA (Java Persistence API). The main purpose of this guide is to make you productive with ObjectDB and JPA in a short time. Guide Structure This manual is divided into

Persistence fields can either be accessed by JPA directly (as fields) or indirectly (as properties and get/set methods). JPA 2 provides an annotation and an enum for setting the access mode: More details are provided in chapter 2 of the ObjectDB manual .

(which is calculated by a query) : Details about all these annotations are provided in Chapter 2 of the ObjectDB manual .

The new ObjectDB Manual describes how to use ObjectDB 2 with JPA. An additional manual that focuses on using ObjectDB 2 with JDO can help JDO users. But since writing a new manual and then maintaining two similar manuals , one for JPA and the other for JDO requires massive work

Support Knowledge Base ObjectDB 1.0 Manual Chapter 7 "JDOQL Queries" Section 7.2 "Query Filter Syntax" Subsection "Fields" Second to last sentence Remove "not" from that sentence.   "An attempt ... for the containing expression but no exception is not thrown."   CBE CBE Great job creating this manual

probable error in text of manual about embeddable classes

. To install a new server check the Manually define a new server radio button (after Run As Run on Server ... ; ObjectDB Explorer : This is the end of the tutorial. Learn more about ObjectDB and JPA by reading the  Manual .

myself and, upon detecting a full JVM GC,  manually evict JdoBlob2s from their relevant PersistenceManager ... , including manually allocating a 1 GB softly referenced byte[] that immediately gets GC-ed on a full GC ... all objects in a manual strong reference list and upon GC detection manually remove the strong

for this type of file, though I can't see a mention of it in the manual . But I've tried creating one as ... It is supported, but not mentioned in the manual , because the new manual focuses on JPA (the old JDO manual

of the UPDATE query manual page : Updating entity objects in the database using an UPDATE query ... is a very basic principle of JPA. See this manual page . You should have read it in the manual ... ).  As I identified (and is noted in the manual you linked) - objects within two separate

: This is the end of the tutorial. Learn more about ObjectDB and JPA by reading the Manual .

Manual . But nevertheless, this class is a valid ObjectDB entity class, despite the warning

: This is the end of the tutorial. Learn more about ObjectDB and JPA by reading the Manual .

by opening it in the ObjectDB Explorer : This is the end of the Eclipse JPA tutorial. Learn more about ObjectDB and JPA by reading the Manual .

the database file in ObjectDB Explorer : This is the end of the tutorial. Learn more about ObjectDB and JPA by reading the Manual .

; ObjectDB Manual , but if you prefer to start by running a live sample application in your IDE

server and open the database file in ObjectDB Explorer : This is the end of the tutorial. Learn more about ObjectDB and JPA by reading the Manual .

of the tutorial. Learn more about ObjectDB and JPA by reading the Manual .

definition in an XML file is missing. This is discussed in the ObjectDB Manual

enabled without specifying a Java agent. This is the end of the tutorial. Learn more about ObjectDB and JPA by reading the Manual .

should be created. See also the ObjectDB manual . support Support Hello, Thank You, I missed that part in the ObjectDB manual . Indeed we've had the File as the parameter. But now ... - that is also the behaviour as described in the manual : "When a string is specified as a value for the target

these manual pages . We do not have specific NetBeans examples in addition to  the tutorials ... this is really the only place to start... ThreaT Ashton Hogan Please consider reading the entire manual ... cannot replace the manual , which has to be read. support Support

printing result 31 [start database explorer on server manually ] 32 searchGoods: start query 33 SELECT u ... on server manually ] searchGoods: start query SELECT u FROM Goods u where u._code like :code code ... explorer on server manually ] searchGoods: start query SELECT u FROM Goods u where u._code like :code

at transaction.commit() if optimistic=true? 5) ObjectDB 1.0 Manual (Support Knowledge Base ObjectDB 1.0 Manual 5. JDO Connections 5.3  javax.jdo.Transaction Automatic Lock Management Last sentence)  ... and therefore ObjectDB 1.0 Manual's  statement suggests datastore transactions (optimistic=false) would be faster

FROM MyEntity e").executeUpdate(); This is implemented since version 2.2.4 but the manual has not ... () cause exceptions. Yes, you'd better to put it into manual , since "drop table" is often in debugging ... the manual . About your other question - I will move it to a separate thread. Please follow the 

file and whole project compilation ? The ObjectDB 2.3 manual gives the following tip ... do not see yet how to relate the manual's example above to these targets and to the various variables ... enhancement. Besides, as the ObjectDB manual says: Enhancement by a Java agent is very easy to use

using bulk update operations must manually update the value of the version column, if desired, and/or manually validate the value of the version column. The persistence context is not synchronized

The following annotations are used to define indexes on persistent fields: The Index Definition section of the ObjectDB manual explains these annotations in details.

specify a value of "0" for the reload attribute. In this case the server has to be restarted manually

to the log if this threshold is exceeded again. Ability to manually select the query plan ... with multiple JOIN operations with very slow execution time you may be able to manually select the best query plans for these queries as a quick workaround. support Support To manually select a query plan