ObjectDB Database Search

51-59 of 59 results


	Selective merge/cascade of detatched entity classes? Merging non dirty objects is expected to be more efficient when classes are enhanced
	Schema migration - long to String change. As a workaround you can read and write (after making them dirty ) all the instances
	Need to close+open database for a commit to be taken into account 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
	Remove a modified entity cause an optimistic lock exception ). Can you explain the optimistic lock exception? It seems that the first level cache contains yet a dirty entity
	Update Entity references if we change the type of an entity to you in a migration process, in which relevant EntityA instances will be marked as dirty and changes
	drop a column from table class you will have to iterate over all the relevant objects, mark them as dirty within an active
	PostUpdate on array changes objectdb.conf file I will revisit the issue of dirty tracking of arrays. However, I have these new
	Best practise loading big data collection) to non dirty entity objects. Can you share a heap dump of your application during
	NullPointerException using with "refresh" method type? What is the status of that object when it is refreshed (clean, dirty , detached, etc.)? Which maps