About fix

issue

Issues with JDO Casting & Full Qualified Names

hi! See this query and the comments about failures. This is really urgent for us because as you've stated, this is the only workaround for now to proper casting AND map KEY access though it isn't working correctly either.. Bug Version: Priority: Normal Status: Closed Replies: 1 Type:  Bug ...

 
issue

Monitoring and Performance counters

After checking last patch from build 2.1.1_01, I started to think about some kind o monitoring tools in ODB. Those tools could look similar to MySQL 'show innodb status', where you can get some informations about how DB is doing. It would be nice to monitor: - inserts/s, updates/s, deletes/s, reads/s - total inserts, update, deletes, reads - I/O operations/s - caches current usage - uptime from last start - caches hit rate - total sessions from clients Feature Request Version: 2.5.2 Priority: Normal Status: Active Replies: 2 Type:  Feature Request ...

 
forum_thread

PersistenceManager.getObjectsById(Collection,boolean) throwing JDOException

I have a call to getObjectsById(Collection,boolean) that is throwing a JDOException the first time I'm attempting to retrieve an object. If I try again, then the second request succeeds. Any idea why this might occur? We're using ObjectDB 2.2.4_02. The collection being passed in is a HashSet<Object> containing a single oid object (the method is written to support multiple objects, but it seems to only be failing irregularly when only a single oid is present). I'm passing false in as the verification argument.... Please try build 2.2.5_02 - it is an attempt to fix the bug but with no test case I cannot tell if it works or not. ...

 
issue

JPQL support for mapped by (inverse) collections

As discussed and demonstrated in this forum thread, collection methods (IS EMPTY, SIZE, MEMBER OF, IN) are not supported for mapped by (inverse) collections.   JPA Feature Version: 2.3.7 Priority: Normal Status: Active Replies: 0 Type:  JPA Feature ...

 
issue

ObjectDB for .NET (C# / VB)

The new file format of ObjectDB 2 has been carefully designed to support multi platform in general and .NET specifically. Work on porting ObjectDB to .NET has started. When it is released - the same database will be available from both Java and .NET and when using client server mode, the client will be have to run one platform where the server is on the other. Feature Request Version: 1.04 Priority: Normal Status: Active Replies: 6 Type:  Feature Request ...

 
issue

Close() Method of EMF throwing "PersistenceException: Connection is closed" on first attempt to close.

We encountered an issue that caused an outage last Friday on multiple ObjectDb server instances. Bug Version: 2.6.9 Priority: High Status: Active Replies: 1 Type:  Bug ...

 
issue

Referential Integrity

Currently ObjectDB doesn't prevent deletion of entity objects that are in use and referenced by other entity objects, and it is the application responsibility to avoid such deletion. During development and testing it is recommended to use the ObjectDB Doctor to verify that reference integrity is not broken and there are no dangling references. Feature Request Version: 2.3.0 Priority: Normal Status: Active Replies: 3 Type:  Feature Request ...

 
issue

ArrayIndexOutOfBoundsException on flush

The following exception was thrown when my app attempted to flush an objectdb database: Bug Version: 1.04 Priority: Normal Status: Closed Replies: 11 Type:  Bug ...

 
issue

Unlimited JPA Persistable Types

I think it would be revolutionary if it were possible to persist any Java object, not just the standard SQL-based objects. Perhaps introducing an annotation will allow for this, something like @BasicType. The ability to store the state of an entire application would be a new innovative approach to persistence. For example, being able to persist: private Thread thread; Since ObjectDB is a proprietary database, surely this could be introduced by adding some sort of equals() override? Feature Request Version: 2.6.0 Priority: Normal Status: Active Replies: 2 Type:  Feature Request ...

 
forum_thread

Query problem after transaction commit

I have a machine running the objectdb server and the client on another machine connect to it. The client program can connect to the server and query to get all the records. However, after transaction.begin ... persist(p) .. commit of a new object, my client program can no longer retrieve the old records but only the latest stored record. I tried to run database explorer on the server machine and able to see all the records including the new stored record.... (e.g. "A"). Please try build 2.6.9_08 that should fix this issue. ObjectDB Support ObjectDB - Fast ...