user manual

Chapter 16: Using BES Properties for CMP 2.x 175
Setting Properties
and Column Properties, which manage persistence. Refer to these properties
below to see where migration issues may appear.
Property Type Default Description
datasource java.lang.String None JNDI datasource name of the
database for this table.
optimisticConcu
rrencyBehavior
java.lang.String UpdateM
odified
Fields
The container uses optimistic or
pessimistic concurrency to control
multiple transactions (updates) that
access shared tables. Acceptable
values are:
SelectForUpdate: database locks the
row until the current transaction is
committed or rolled back. Other
selects on the row are blocked (wait)
until then.
SelectForUpdateNoWAIT: database locks
the row until the current transaction is
committed or rolled back. Other
selects on the row will fail.
UpdateAllFields: perform an update on
all of an entity's fields, regardless if
they were modified or not.
UpdateModifiedFields: perform an
update only on fields known to have
been modified prior to the update
being issued.
VerifyModifiedFields: verify the entity's
modified fields against the database
prior to update.
VerifyAllFields: verify all the entity's
fields against the database prior to
update regardless if they were
modified or not.
Pessimistic concurrency specifies the
container to allow only one
transaction at a time to access the
entity bean. Other transactions that
try to access the same data will block
(wait) until the first transaction
completes. This is achieved by
issuing a tuned SQL with FOR UPDATE
when the entity bean is loaded. To
achieve pessimistic concurrency set
SelectForUpdate or
SelectForUpdateNoWAIT.
useGetGenerated
Keys
java.lang.Boolean False Whether to use the JDBC3
java.sql.Statement.getGeneratedKeys()
method to populate the primary key
from autoincrement/sequence SQL
fields. Currently, only Borland
JDataStore supports this statement.