ObjectDB Database Search

a PersistenceManagerFactory? Dave dmoshal David Moshal Couple of additional points : 1. the database

which point to my shared object db development instance. I do this manually but I have a half-working

down server/client jar version mismatches)     dmoshal David Moshal Good point . Build 2.2.4

Hi, I found a problem in ObjectDB which may be incompatible with EclipseLink and JPA. The type nodes2 derives from nodes1, the type nodes1 derives from nodes. Whether the number is random may be not important. The point is adding 10 nodes2 + 10 nodes1 + 10 nodes resulting no nodes1 from ObjectDB

This is a good point . Notice that the most portable generation strategy is TABLE , because: AUTO - each JPA

the point at which the stateful session bean that declares a dependency on an entity manager of type

to the plugin runtime classpath. Fixing  "SELECT p FROM Point p" to  "SELECT p FROM Pilot p

hi   from time to time i get exception during online backup in server/client config: Exception in thread "Thread-0" com.objectdb.o.UserException: Failed to read from file 'D:\twozniak\Desktop\db\objectdb-2.2.8\db-files\ points .odb' at com.objectdb.o.MSG.d(MSG.java:74) at com.objectdb.o.LFL.T

') AND ($3.valueAsString='Baldwin'))) There is nothing in the database at this point . I was capturing

with JPA and I'm wondering if you might be able to point me to something on the RDBMS mapping

point - falling back to serialization (automatically, unintentionally) causes a lot of problems. 

.! That is a good point . After changing the class and before running the Doctor - the class

content but renaming the classes are renamed e.g. Point - ODBPoint and ELPoint JFK John Francis

one could set when creating a new ObjectDB datafile? andrej Andrej Gabara This is a good point

to rename the Entity Classes (especially the package names). dmoshal David Moshal One further point : I'm

where an entry points to an to-be-removed OtherEntity, to remove it from the Set manually? Hope not

, I'll create a new one. pedwards Paul Edwards From your point of view everything that is related

three Test Entities whereas first one points to Hint{name=A}, second one to Hint{name=B

the TopLevelClass does still keep the old name why?? I was under the impression that they both point

Hi there, Our app is highly scalable and can be distributed among multiple processes on multiple machines. ObjectDB Server is not really scalable right now and would be a SPOF for our application. So, we'd like to embedded odb into each instance instead for now and point each to the same database

can be specified by type and primary key separated by # (e.g. Point #1). A collection can be specified as

"MetadataString" (see attachments). But actually, there is no point in my continuing the evaluation

to read and more IDE portable. However, regarding your second point , properties can be used

per minute, at which point the process is essentially hanging - see attached screenshot. 13:22:43 - 13

.objectdb.o.PGC:w: line number 232) is less clear. It points to a synchronized statement. Maybe

Hi, The documentation is lacking in this respect. How do I configure where the ObjectDB database file is stored. I need to know where it is so I can inspect it with 'database explorer'. The docs say to set it to "$objectdb/db/ points .odb" and that this defaults to "the installation directory

("$objectdb/db/ points .odb", config); EntityManager em = factory.createEntityManager(); for (Class x

;password=password" and the above config.   I was expecting I should be able to point that slave

still get error in Eclipse that points to pom.xml part (execution line): org.codehaus.mojo exec-maven

is wrong. I realized that some time after the post. Sorry for false alarm and thanks for pointing error in my model. lwalkowski Lukasz Walkowski

a performance point of view. JonMoore Jonathan Moore A similar problem is discussed in this forum thread

on roadmap Support for http://java.net/jira/browse/JPA_SPEC-28 So are those points on your roadmap

the objects. At some point , may be when restarting Glassfish or re-publishing the application, the database

and re-setting some properties to entities from the collection. NPE is thrown at some point

= Persistence.createEntityManagerFactory("objectdb:/var/tmp/ points .tmp;drop"); EntityManager e = emf

to fill all my classes with redundant fields and their relative getters and setters.  But at this point

have either (I'm using ObjectDB 2.4.4_15 atm). Please can someone point me into the right direction? Thank

itself. Then if we ever have to boot up another instance, we can point objectdb of those new instances at the first instance as

I'm getting the ClassCastException below when querying objects. As yet I haven't been able to track down the exact circumstance in which it occurs - saving and querying objects works fine on attempts to recreate - but presumably at some point an object gets saved which objectdb doesn't like. Any

in some cases it does cause problems. Could you please provide more details on the last two points

an instance of point on the chart PointEntity latestPoint = new PointEntity(moment); latestPoint.setX(x

sizes (not just the page cache) in the configuration. support Support Fair point - I hadn't considered

Added support for using ObjectDB with JBoss AS 7.0 . Sample databases (world.odb, points .odb) included in ObjectDB distribution. New default Explorer colors (apply with Tools Options Fonts Reset All). New menu for accessing local databases (in $objectdb/db ) in the Explorer. Improved

? Could you give me some information around what is happening at this point so I can try to avoid the block

() of the CriteriaQuery at different points in time, it happens that we get the same identifier (namely, $1

and restart.   support Support hi, Perfect, thank you very much! Now the only point left

me a starting point at least - and will let you know if/when I have any success. felixobjectdb

have pointed out the problem.  It's comes from the "enum" type which is not correctly taken into

When a large transaction is committed, ObjectDB increases some internal structures, i.e. allocates more memory, but from that point the structures remain big and the memory is not released even if all the next transactions are small. This problem was found during a heap analysis (see #9 in

I'm having trouble creating a simple test case that reproduces it.  At this point , I think