ObjectDB ObjectDB

Internal Website Search

71-80 of 200 resultsRefresh
21

Selective merge/cascade of detatched entity

for this approach). All potential changes are checked with application logic before being committed to the database, so a commit will never fail. Any time an object is modified it is checked that the modification would be valid, and then committed. Lets assume I have many Salesmen, and add a new
7

ObjectDB Website - Terms and Conditions of Use

not, however, make any commitment to update the materials. 6. Links ObjectDB Software has not
7

Database Explorer

> Save menu command commits the transaction (applying all the changes to the database). The File
6

javax.persistence.LockModeType

that row and obtains the modified value, before T1 has committed or rolled back. Transaction T2 eventually commits successfully; it does not matter whether T1 commits or rolls back and whether it does so before or after T2 commits. P2 (Non-repeatable read): Transaction T1 reads a row
4

javax.persistence.CacheStoreMode

the behavior when data is read from the database and when data is committed into the database ... /update entity data into cache when read from database and when committed into database. Insert/update entity data into cache when read from database and when committed into database. Forces refresh
4

javax.persistence.EntityTransaction

- if isActive() is true Since: JPA 1.0 void commit() Commit the current resource transaction, writing any unflushed changes to the database. Commit the current resource transaction, writing any ... - if the commit fails Since: JPA 1.0 boolean getRollbackOnly() Determine whether the current
4

javax.persistence.FlushModeType

those entities to the database or by some other means. If FlushModeType.COMMIT is set, the effect ... execution. Since: JPA 1.0 FlushModeType COMMIT Flushing to occur at transaction commit. Flushing to occur at transaction commit. The provider may flush at other times, but is not required to. Since: JPA 1.0
1

Step 4: Add a Servlet Class

.getTransaction().commit(); } // Display the list of guests: List
0

javax.jdo.Constants

2.1 String PMF_ATTRIBUTE_DETACH_ALL_ON_COMMIT The name of the persistence manager factory element's "detach-all-on-commit" attribute. The name of the persistence manager factory element's "detach-all-on-commit" attribute. Since: JDO 2.1 String PMF_ATTRIBUTE_IGNORE_CACHE The name of the persistence
0

javax.jdo.listener.StoreLifecycleListener

during javax.jdo.PersistenceManager.flush or javax.jdo.Transaction.commit. Invoked whenever a persistent ... .commit. It is called after the field values have been stored. Parameters: event - the store event ... is stored, for example during javax.jdo.PersistenceManager.flush or javax.jdo.Transaction.commit

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