ObjectDB Database Search

Hello, we can't understand why the performance of queries is not the best and the execution requires so much memory. In the implementation of our UnitTests we have used " DELETE FROM Object" to delete the database. That did not work because we often get an "out of memory" exception

Hi, I have deleted an instance of ClassA . However, if I try to access ClassB , which has a field of type ClassA , ClassB.classA , then, rather than getting a null pointer for classB.classA , I ... are removed/ deleted from the databases - it is the application responsibility to clear any references

; em.createQuery(" delete from Street s").executeUpdate();         em.createQuery(" delete from Location l").executeUpdate();        

Hello, we have questions about the file size of ObjectDB database on disk. Can you tell us something about how the deleting of entities affects the size of *.odb files on disk? -Will the released ... ; We have created a small test, in which we create and delete entities. It looks like that the released memory

, it is deleted from the database, no matter if it's referenced by an instance of Employee. I tried to use ... integrity and it is the application responsibility to avoid such deletion . The ObjectDB Doctor

is still there. If you try to manually delete the folder, you will get an "Folder in use" error message. Because the "odbxxxxxx.log" file is in use by an java process. If I restart Glassfish, I can delete the folder

file never shrinks when large number of objects are deleted and the only way to reclaim that space ... some minor helpful context to propose an answer.) CBE CBE ObjectDB reuses space of deleted objects

, Deleted , and Changed. That is a simple example, more complex views are composed of data from ... of the Company and User entity classes. Next a request comes in which deletes a company. So we need

in repair mode. It does not helped unfortunatelly. What helped was deleting the entity completely in explorer including all it's instances ( deleting only instances did not helped) But that way

Hello, why delete from ... doesnt modify size of odb? Even in in embedded mode, and in server mode i use recovery, not recording mode. mastervoland Vladimir Sadovnikov When objects are deleted from the database their space is marked as unused and becomes available for future objects. The size

= OdbError631.class.getSimpleName() + ".odb";         new File(dbName). delete ();         new File(dbName + "$"). delete ();      

. You should be able to delete old recording files unless they are needed for slave servers ... . And sometimes I use " DELETE lvl FROM level lvl" to reassemble level data (it sometimes has some

delete it and restart the database server. Version 2.3.1 is nearly one year old - you should upgrade ... bytes). confirmed that problem is resolved when the recovery files are deleted , does'nt seem to be any

ObjectValue are just deleted from the database. If I had detailled traces of the EntityManager or of ObjectDB, I could identified when the delete operation is executed! There is still something I don't

= CascadeType.REMOVE) Address entities used Employee (id=1) deleted , but Address (name_2) using other Employee (id=2) deleted too: [Address{name='name_1'}, Address{name='name_2'}, Address{name='name_3

. How can I remove this embeddable class without deleting my database or deleting the entity

with the deleting of indexes and mixed index/statistics creating what can be seen in the log) - the behaviour ... with the deleting of indexes and mixed index/statistics creating what can be seen in the log) The log file indicates

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.   

Hi, When deleting an entity "Mitglied" - everything works fine. Trying to delete another one (in a separate transaction) always causes a NullPointer Exception in __odbGetNumMember line 1 of the enhanced Mitglied class. I am unable to replicate it in a simple testcase but it always happens in

and the os allowed us to delete the files in question without any problem. In this case we weren't ... ? support Support It was repeatable at the time but we ended up deleting the odb$ to get the app started

? What combination of DELETE / INSERT / UPDATE operations are in that huge transaction? Can we assume ... ; What combination of DELETE / INSERT / UPDATE operations are in that huge transaction? Possible

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

) . delete ( ) ;          new File ( dbName + "$" ) . delete ( ) ;  

) - some of these references are broken when we delete objects - there is a mechanism in our application ... on deleting are very high. is there a problem to have this kind of broken references ? hgzwicker Hans-Georg

to explicitly define the classes, in the schema config (objectdb.config), that should be deleted .   In ... . 1) How can we delete a whole class? 2) What happens when we open the DB but not all entity classes

. It may be possible to improve the Doctor in a way that these two objects will be deleted (not fixed ... . Sometimes everything is just fine. And just now I got (after deleting the database file and re-running the application

: for single read/write/update/ delete : - we create new EntityManager, do the operation in transaction ... (if not exists), do the operations using EM in ThreadLocal, on batch end we commit transaction, delete from

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