ObjectDB ObjectDB

Internal Website Search

101-110 of 200 resultsRefresh
5

Wrong data stored in time only fields

This may be related to the fix for the problem described in this thread: Wrong data stored in date only fields. The object and its date and time fields are the same as in the referenced thread ... are using the 2015g time zone data. While we cannot see a problem with date only fields (more testing
1

Database Server

: > java -cp objectdb.jar com.objectdb.Server If objectdb.jar is not in the current directory a path
1

setParameter(param, value, temporalType)

Method javax.persistence.TypedQuery TypedQuery<X> setParameter( Parameter<Date> param, Date value, TemporalType temporalType ) Bind an instance of java.util.Date to a Parameter object. Parameters: param - parameter object value - parameter value temporalType - temporal type Returns: the same query
1

setParameter(param, value, temporalType)

Method javax.persistence.Query Query setParameter( Parameter<Date> param, Date value, TemporalType temporalType ) Bind an instance of java.util.Date to a Parameter object. Parameters: param - parameter object value - parameter value temporalType - temporal type Returns: the same query instance
1

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
0

javax.persistence.EntityManager

is a managed entity instance belonging to the current persistence context. Check if the instance is a managed entity instance belonging to the current persistence context. Parameters: entity - entity ... : flushMode Since: JPA 1.0 LockModeType getLockMode(Object entity) Get the current lock mode
0

javax.jdo.Transaction

control should be used for the current transaction, whether instances may hold values in the cache ... void commit() Commit the current transaction. Commit the current transaction. Throws: JDOUserException ... for this Transaction instance Since: JDO 1.0 boolean getRestoreValues() Return the current value of the restoreValues
0

javax.jdo.datastore.Sequence

of additional values to allocate Since: JDO 2.0 Object current() Returns the current sequence value object if it is available. Returns the current sequence value object if it is available. It is intended to return a sequence value object previously used. If the current sequence value is not available, throw
0

javax.jdo.spi.StateInterrogation

the application or the data store, then the ObjectId returned is only valid within the current ... instance has been deleted. Instances that have been deleted in the current transaction return Boolean ... if the parameter instance was deleted in the current transaction. Since: JDO 2.0
0

javax.jdo.FetchGroup

, and BigInteger; as well as Date and its jdbc subtypes and Enum types. Since: JDO 2.2 String DEFAULT ... . The Set is a copy of the currently defined members and will not change based on subsequent changes

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