Internal Website Search

()); } } itsme Martin Petzold Somehow this Log class is not identified as an entity class. Maybe ... is already very limited. The class has already been identified as non-persistable when the database was opened

Hi, I have reasons for sometimes trying to query the database before anything has been created. The problem is the database throws a InternalException when that happens. Is it possible to throw something that identifies that that is the issue, say something like "MissingSchemaException", ie

your computer MAC address. Using MAC address as a machine identifier is a common practice in

during development and testing can help in identifying failures. If the Doctor reports broken references

, until you can identify the specific part of the application that is relevant to the failure. support

just removing the error is not enough and some analysis is needed in order to identify the order

." appears. I have attached a RAR archive with more logs. I hope this helps to identify the problem

whatever check to identify previously deleted Entity instances profile = ....; // create new Profile

ObjectDB in order to identify this conflict that your test demonstrates. support Support

can help in identifying conditions that require a fix during development. You may subscribe to this new

The resource identified by this request is only capable of generating responses with characteristics not

should identify the parameter as a date parameter and replace the text field in that case automatically with a date editor. support Support

Ran into the problem again. Suddenly, on my development laptop, objectdb required me to regenerate a new license!   dmoshal David Moshal Try to activate ObjectDB again on your development laptop. Maybe this activation will reveal the unexpected changes that cause ObjectDB to identify the laptop as a different machine.   support Support

).  As I identified (and is noted in the manual you linked) - objects within two separate

, because an object is identified as dirty by comparing its old content with the current content. With enhanced

can identify it correctly with enhanced classes but not with classes that are not enhanced. Note

Support Hi, we identified the problem to be on our end: The OSGi Framework Manifest was a missing

so you cannot identify the process of each temporary directory. In that directory a lock file, lock.lck

;this is not done when using a debugger. ObjectDB identifies a database file that was not closed by

().begin(); for ( Identifiable o : entityCollection) { if (o.getIdentificator() == null) { em.persist(o

. Could you please assist us in identifying the cause of these performance issues and suggest any possible

and open a new one if you think it could help. support Support I have identified that the problem lies

of ObjectDB, I could identified when the delete operation is executed! There is still something I don't

createEntityManagerFactory method asks ObjectDB if it knows that persistence unit - ObjectDB cannot identify it as

there were very few of them, which we could not identify , but only at one timestamp which does not correspond to times of increasing sockets used

dansmith Daniel Smith The combination of (type, ID) should identify entity objects uniquely

. There is still a question why StringIdentity is not identified as a subclass of  SingleFieldIdentity in #7

in the Doctor that caused identifying objects after field type change as invalid were removed in

in identifying such problems. The fix, however, is required at the application level. support

, however, that internally ObjectDB identifies simpler date/time instances, such as in your question, and their storage consumes less space. support Support

of the entity object when it is loaded in order to identify changes on commit. In previous versions

Is it possible for an ObjectDB PersistenceManger/EntityManager to connect to more than one database at a time? Also, can objects in one database reference objects in another database (e.g. through globally unique identifiers )? jonb Jon Brumfitt You can use as many databases as needed

/ identify this problem, as I did not imagine that performing the load access inside an if statement

._PersistenceException: Unexpected query token 'type': Identifier is expected at com.objectdb.o.JPE.g

and fetch its services. Demand object is identified and found correctly, but as it is associated

only mode. This requires some operations by your application: identifying a failure, moving

It is getting more and more frustrating :( We've introduced distinct select instead of regular selection in our code (no changes else) and suddenly receive invalid identifiers in queries exceptions ... () of the CriteriaQuery at different points in time, it happens that we get the same identifier (namely, $1

van woerkom Unfortunately the information in this stack trace is not sufficient to identify

specified in the configuration . Can you identify specific circumstances in which this happens? support

cause of these Exceptions and identify why they are not showing up in the ODB log

Hi, As I've feared.. Fully Qualified Names in casting not working, throws an identifier expected exception: package com.test; import java.util.HashMap; import java.util.Map; import javax.persistence.Embeddable; import javax.persistence.Entity; import javax.persistence.EntityManager; import javax

machine and identify unusual activity at the server when that happens? e.g. other operations

ways to improve the check to identify and warn against partial enhancement in future versions

When I run the following code: EntityManager em = getEm(); Customer result = null; try {     logger.debug("Ident: "+ident);     result = em.createQuery("Select c from Customer c where c. identifier =:id", Customer.class).setParameter("id", ident).getSingleResult

when the slow removal happens? It may help to identify the exact build in which this issue is started. 2

to identify the state of an entity object by exploring it in the debugger. support Support After running

. How are these two stack traces related? Can you identify a problematic query that caused the problem? support Support

these exceptions, maybe you can identify them by getCause() , since the underlying exception could be different

, and unfortunately the Doctor doesn't include checks to identify this mismatch. However it is very easy to fix

Added support of entity collections as query parameters. Added support of running ObjectDB within Eclipse 3.7 wrapper jar . Added support of sharing an identifier name for a variable and a parameter in the same query. Added support for using ObjectDB with GlassFish 3.1.2 . Added handling missing