|
Very fast in memory sequence manager implementation, only the first
time an id was requested for a class, the manager query the database
for the max id in requested column - all following request were
performed in memory.
Limitations:
- do not use in clustered environments
- do not use if other applications generate id's for objects
Implementation configuration properties:
Property Key |
Property Values |
seq.start |
Set the start index of used sequences (e.g. set 100000, id generation starts with 100001).
Default start index is 1.
|
autoNaming |
Default was 'true'. If set 'true' OJB try to build a
sequence name automatic if none found in field-descriptor
and set this generated name as sequence-name
in field-descriptor. If set 'false' OJB throws an exception
if none sequence name was found in field-descriptor.
|
sequenceStart |
Deprecated, use property 'seq.start'. Set the start index
of used sequences (e.g. set 100000, id generation starts with 100001).
Default start index is 1.
|
See Also: org.apache.ojb.broker.util.sequence.SequenceManager See Also: org.apache.ojb.broker.util.sequence.SequenceManagerFactory See Also: org.apache.ojb.broker.util.sequence.SequenceManagerHelper author: Armin Waibel version: $Id: SequenceManagerInMemoryImpl.java,v 1.14.2.3 2005/12/21 22:28:41 tomdz Exp $ |