About ORDER BY

101-110 of 200Refresh
JDO Doc
6

javax.jdo.JDODataStoreException

this method in order to produce a locale-specific message. For subclasses that do not override ... [] getNestedExceptions() The exception may have been caused by multiple exceptions in the runtime. The exception may have been caused by multiple exceptions in the runtime. If multiple objects caused the problem
JDO Doc
6

javax.jdo.JDOException

it to return a cause set by some other means. This is appropriate for a "legacy chained throwable ... order to produce a locale-specific message. For subclasses that do not override this method ... () The exception may have been caused by multiple exceptions in the runtime. The exception
JDO Doc
6

javax.jdo.JDOUserException

this method in order to produce a locale-specific message. For subclasses that do not override this method ... () The exception may have been caused by multiple exceptions in the runtime. The exception may have been caused by multiple exceptions in the runtime. If multiple objects caused the problem, each
JDO Doc
6

javax.jdo.JDOFatalException

. Creates a localized description of this throwable. Subclasses may override this method in order ... may have been caused by multiple exceptions in the runtime. The exception may have been caused by ... [] getStackTrace() Provides programmatic access to the stack trace information printed by printStackTrace
JDO Doc
6

javax.jdo.JDOOptimisticVerificationException

. Creates a localized description of this throwable. Subclasses may override this method in order ... may have been caused by multiple exceptions in the runtime. The exception may have been caused by ... [] getStackTrace() Provides programmatic access to the stack trace information printed by printStackTrace
Forum
6

Suspected memleak caused by bad state of EntityManager

and using. We find a slow memleak in our application recently, and by trace of Entity construct and finalize, we found the problem is caused by bad state of EntityManager. After first throwing ... and retrieved by EntityManagerFactory, and the instances of Entity constructed by ObjectDB
Forum
6

Merge of entity classes with "mapped by" very slow

Hi, I have found a strange behavior when merging entities with "mapped by" set on @OneToMany ... - one with mapped by, second with adding entities list without "mapped by". The difference is huge event for such small objects - 2ms (without mapped by) vs ~50ms (with mapped by) Is there any chance
JPA Doc
6

javax.persistence.LockTimeoutException

: Serializable Thrown by the persistence provider when an pessimistic locking conflict occurs that does ... it to return a cause set by some other means. This is appropriate for a "legacy chained throwable ... a localized description of this throwable. Subclasses may override this method in order to produce
JPA Doc
6

javax.persistence.QueryTimeoutException

: Serializable Thrown by the persistence provider when a query times out and only the statement ... a cause set by some other means. This is appropriate for a "legacy chained throwable" that predates ... a localized description of this throwable. Subclasses may override this method in order to produce
JPA Doc
6

javax.persistence.NonUniqueResultException

Interfaces: Serializable Thrown by the persistence provider when Query.getSingleResult() or TypedQuery ... , a subclass can override it to return a cause set by some other means. This is appropriate for a "legacy ... this method in order to produce a locale-specific message. For subclasses that do not override this method