ObjectDB Database Search

the database. ie: which objects, and which collections of objects, have been dirtied . in the jdo api ... ) so you can check if an entity object is dirty using the static JDOHelper.isDeleted method. support Support ... object is dirty using the static JDOHelper.isDeleted method. excellent, thanks! another question

phenomena can occur: P1 ( Dirty read): Transaction T1 modifies a row. Another transaction T2 then reads ... must ensure that neither of the following phenomena can occur: P1 ( Dirty read): Transaction T1 modifies

dirty : // Object state is: Nontransactional-Clean entity.removeIf(item - false); // Object state is: Persistent- Dirty When we use removeIf on a large number of objects, for which only a small % actually ... would match the predicate before calling removeIf. Would it be possible to mark the object as dirty

, these changes will not trigger making the containing entity object dirty , but if it is marked dirty ... Support I'd like to understand the " dirtying " of entities a little better.  If an array reference ... that is the same as the old value, will the entity be marked dirty ?  If I want to avoid

(){ softReferenceData = new SoftReference (data); data = null; } @Override public void jdoPreStore(){ // A dirty ... objects unless necessary (e.g. for dirty objects until commit). On the other hand the data store page

program that retrieves all the relevant containing entity objects, makes them dirty and persists ... the schema and wrote the program which retrieves the containing entities, made them dirty

to you in a migration process, in which relevant EntityA instances will be marked as dirty and changes

Hi, I have one case where commit (update of entity in this case) is not taken in account unless database is actually closed and re-open, no error. I tried to use flush instead of close+re-open but it does not work. So currently there is a dirty close + open + reload on each update

class you will have to iterate over all the relevant objects, mark them as dirty within an active

objectdb.conf file I will revisit the issue of dirty tracking of arrays. However, I have these new

). Can you explain the optimistic lock exception? It seems that the first level cache contains yet a dirty entity

it becomes a regular java.util.Array again which of course doesn't mark the object dirty when getting changed

file size = 297009152, dirty pages = 1, update list s = 2, dirty page map = 1,   FastModel Ben

included a dirty and quick fix that used  get as a prefix for both get and set  persistent

type? What is the status of that object when it is refreshed (clean, dirty , detached, etc.)? Which maps

collection) to non dirty entity objects. Can you share a heap dump of your application during