ObjectDB Database Search

responsibility to prevent broken references. When an OtherEntity object is deleted the application

for all of those. So i'm still a bit confused on why this file lingers and why I can't delete it without waiting

java I assume that if I'll back up the .odb file, delete it and then restore it will fix the issue

database. support Support Looking through the code, there is no other 'point' declared. I deleted the db

server because Netbeans kept deleting my database each time I deployed with stand-alone mode

the collection and not delete any of the Readings from the DB. Also, refreshing or reading

indicates that the database is not corrupted. The two missing objects are probably the result of deleting

.ObjectdbTest.main(ObjectdbTest.java:42) sjzlondon Steve Zara There was a bug in handling JDO delete

;  odbFile. delete ();         EntityManagerFactory emf

;  new File("objectdb:$objectdb/db/test3.tmp"). delete ();        

Hello, I deleted the database a few times, so there are no Guests from before I added the list

time ago and they were never really used. I deleted them from Java source code, but there are still in

because there was only one project in it. I suppose deleting the class files in the bin directory

the right format. You may delete it from your server. support Support No issues were found in the heap

-modular ( delete module-info) and included the objectdb.jar in the classpath. The program works now. Thanks for the help :) Sweetwater Marc

#453 ). Completed missing documentation (e.g. UPDATE & DELETE queries). Fixed memory leak issues

.apply(em) will do stuff like persist, delete , etc.  I only have 1 instance of emf.   

I apologize if this post is 'out of order'. If so, the moderators should feel free to delete it. I am sure that my recent questions have shown my incompetence with ObjectDB (although I have used many other SQL and non-SQL databases). Therefore, my questions must seem trivial. So often one sees

the compiler back to 1.8, deleted module-info.java, and put objectdb on the classpath, the application

) ... 1 more dmoshal David Moshal This issue resolved when I deleted the old database (it was just

delete a slave to change the redundancy of the clustering without restarting. TIA gzdillon Lai Yang

the vacuum. If there is no way to do this other than manually implementing code to read, delete , and write

(QuantServerImpl.getInstance().getCompanyDB());     // delete all the backups in the backup dir

after index deletion . Changed default configuration (enabled recovery, disabled recording). Fixed

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

navigation through a broken reference (probably a reference to a deleted object) during query execution

Fixed an exception due to to an unused type referencing a deleted type.

- the map is loaded and its contents are printed. On the second run (without deleting or clearing

could be to store many large objects and then to delete them, creating more space and avoiding resizing

Added support of navigation through collections  (as a JPQL extension). Added version display to the Server and Explorer About dialog boxes. Fixed an UPDATE/ DELETE query bug in client-server mode. Fixed an ArrayIndexOutOfBoundsException in retrieval of large objects. Fixed Explorer display

to memory leak ( issue #453 ). Completed missing documentation (e.g. UPDATE & DELETE queries). Fixed

Added initial support of Record entities. Implemented a new query method:  containsAnyKey . Improved field type error and internal error messages. Improved the Doctor output. Fixed a bug in using inner classes for query results. Fixed an error due to to an unused type referencing a deleted

Added an option to disable temporary file deletion . Added support of using entity classes with missing dependent types. Added support of composite indexes with components of different lengths . Fixed a bug in reflection mode in detecting changes after flush ( issue #1602 ). Fixed

.  Based on the implementation, you will need to delete the odb file between each execution

Fixed an exception due to to an old interface referencing a deleted type.