ObjectDB Database Search

a previous schema version. The fields are identified by their names only. If you add a new persistent ... then it will not remove the field as ObjectDB will identify it as an old schema. Anyway, this is not

()); } } 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

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

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

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

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

;               I have to use identified ip

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

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

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

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

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

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

_ identifier ; Integer version_no; Integer possible_extension; Integer cancelled; Integer booking_status

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

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

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

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

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

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

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

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

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

cookies that are used to identify a logged in user. I use Chrome and do not have that problem

my part to identify a bug  I just reported a different one (hopefully the right one) http://www.objectdb.com/database/forum/811 Thanks EKK Emmanuel Keskes

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

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

, 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

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

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

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

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

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

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

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

of all or at least the relevant threads)? Does VisualVM identify a deadlock? support Support

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

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

.model.account.contact.IndividualContactDebitorAccountFragment': Identifier is expected SELECT COUNT

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

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

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

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

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

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

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

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

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

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