ObjectDB ObjectDB

Internal Website Search

71-80 of 200 resultsRefresh
12

Possible cause for "Enhancement of type ... is old and cannot be used"

the problem some months ago as an issue report at: BUG: objectdb-2.6.6_07: FAILS on @OneToMany ... to fix it in build 2.6.6_08. I reported today on investigations by version here: http://www.objectdb.com ... Darren Kelly The issue that was reported and demonstrated by that support ticket was getting
2

ObjectDB License Agreement [ver. 2.0.4]

, product brochures, financial reports and other promotional materials. 8. This agreement is effective
2

FROM clause (JPQL / Criteria API)

, that if the Country and Capital objects are needed only for their names - the following report query
2

again merger missing logs + objectdb exception

(or generated backups) and report any errors except the expected broken references error. support ... exception (Error 990) Generated by Java HotSpot(TM) 64-Bit Server VM 1.8.0_91 (on Windows Server 2012 R2 6.3). Please report this error on http://www.objectdb.com/database/issue/new com.objectdb.o
2

com.objectdb.o.InternalException: null

] Unexpected exception (Error 990)   Generated by Java HotSpot(TM) 64-Bit Server VM 1.8.0 (on Mac OS X 10.9.2). Please report this error on http://www.objectdb.com/database/issue/new com.objectdb.o ... ] Unexpected exception (Error 990)   Generated by Java HotSpot(TM) 64-Bit Server VM 1.8.0 (on Mac OS X 10.9.2
0

Step 1: Install BIRT and ObjectDB Driver

to the ObjectDB server version when using client-server mode. The next step is creating a BIRT Report project.
0

Step 3: Create an ObjectDB Data Source

. The next step is using this data source to create a data set for the BIRT report.
0

javax.jdo.annotations.Join

: the vendor extensions Default value: {} Since: JDO 2.1 String foreignKey Name for a generated foreign key constraint. Name for a generated foreign key constraint. Returns: the name of the generated foreign key constraint Default value: "" Since: JDO 2.1 String generateForeignKey Generate or assume
0

[ODB1] Chapter 3 - Persistent Classes

methods that perform the same accesses but also report to ObjectDB. Tracking changes in persistent
0

javax.jdo.annotations.Element

: the vendor extensions Default value: {} Since: JDO 2.1 String foreignKey Name for a generated foreign key constraint. Name for a generated foreign key constraint. Returns: the name of the generated foreign key constraint Default value: "" Since: JDO 2.1 String generateForeignKey Generate or assume a foreign

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