About trigger
JPA Lifecycle Events
Explains how to use JPA lifecycle events (client side triggers) with callback methods and listener classes. Callback methods are user defined methods that are attached to entity lifecycle events and are invoked automatically by JPA when these events occur. This page covers the following topics: Internal Callback Methods ...
javax.jdo.listener.InstanceLifecycleEvent
This is the event class used in life cycle event notifications.(Class of JDO)
javax.persistence.spi.ProviderUtil
Utility interface implemented by the persistence provider.(Interface of JPA)
enhanced object .. NOT enhanced
Hi I think I have found a bug : - I have enhanced a class but when I tried to persitst it I got an error that this class has not been ehanced (what is important, this class has _odbTracker field added) So, instead of DB write a standard serialization mechanizm is triggered. Finnally we get an OutOfMemory expeption. b #1 2011-08-08 08:22 Hi I think I have found a bug : - I have enhanced a class but when I tried to persits ...
Safe Settings
Hi, I am trying to set up ObjectDb in a safe way that allows turning the machine off while database transactions are running. I would like to test if things are really safe and if I don't get corrupted database files in any possible case. I found "recovery" and "recording" in the objectdb.conf file. Which one is safer to use? I suppose I should turn on sync="true", right? #1 2011-03-28 16:05 Hi, I am trying to set up ObjectDb in a safe way that allows turning the machine off while database trans ...
Time Sequence Object Command DB
We (www.s2ssystems.com) have a time-sequential object command database. I would like to see if it can be built and run efficiently on ObjectDB. The requirements that drive the design of this database are: ... commands. Method commands are generally used to trigger creation of transient objects. The database can be ...
isLoaded(entity)
If the provider determines that the entity has been provided by itself and that the state of all attributes for which FetchType.EAGER has been specified have been loaded, this method returns LoadState.LOADED.(Method of javax.persistence.spi.ProviderUtil)
When using inheritance, you can specify, which ID to use
When storing objects with inheritance, it should be possible to choose, which ID (parent or child class) should be used for new object. For example: public EntityA() { @Id long id; String field1; } ... will be generated from EntityA. It should be possible to trigger generating ID from child entity, for example like this: public ...
isLoadedWithoutReference(entity, attributeName)
If the provider determines that the entity has been provided by itself and that the state of the specified attribute has been loaded, this method returns LoadState.LOADED.(Method of javax.persistence.spi.ProviderUtil)
InstanceLifecycleEvent(source, type)
Creates a new event object with the specified source and type.(Constructor of javax.jdo.listener.InstanceLifecycleEvent)
