Home » Search

About trace

141-150 of 200Refresh
Result
1

ObjectDB version 2.5.0

an query IN expression. Added the ability to disable hollow objects. Added TRACE level logging
Forum
1

2.7.3_03 Erroneous "Attempt to modify a primary key of a managed object"

logging mode should be sufficient to see reported errors. The stack trace in #11 is normal in debug
Issue
1

[ObjectDB 2.4.1] Unexpected exception (Error 990)

(RemoteTestRunner.java:197)   The stack trace indicates a missing (or empty) FROM clause in a DELETE
Issue
1

[ObjectDB 2.4.1] Unexpected exception (Error 990) on getObjectById

.objectdb.jdo.PMImpl.getObjectById(PMImpl.java:410) ... Ideas welcome. The stack trace indicates
Issue
1

[ObjectDB 2.5.6_05] Unexpected exception (Error 990)

you for your report. The stack trace includes an automatic request to report the error, but actually
Issue
1

[ObjectDB 2.6.0_04] Unexpected exception (Error 990) com.objectdb.jpa.JpaQuery.getResultList

.eclipse.equinox.launcher.Main.main(Main.java:1438)     This stack trace indicates an unexpected
Issue
1

[ObjectDB 2.6.7_04] Unexpected exception (Error 990)

you for this report. The stack trace indicates an unexpected condition at the end of a flush operation
Forum
1

An ArrayIndexOutOfBoundsException with nested entities and enhanced entities

-trace and can help to create (fast) a reproducible sceanario. It looks again as a mismatching
Forum
1

An InternalException occurs when gets an result list

about the query? The stack trace indicates an unexpected query variable. Are there non entity
Issue
1

Another NPE on em.createQuery(query).getResultList()

and this time I will need more than the stack trace. I am checking out the test. How exactly should I run