Jonathan,

I'm enjoying the discussion - but on the topic of verified
updates, maybe its an idea in the Borland AppServer (next
release?) to set the default optimistic concurrency behavior to:
"VerifyAllFields" that performs an update along the
lines of:
"UPDATE <some_table> SET (only_changed_fields) WHERE
<all_table_column_values_are_values_read_in_at_start_of_transaction>"

instead of the current default "UpdateModifiedFields" which
performs an update along the lines of:
"UPDATE <some_table> SET (only_changed_fields) WHERE
<primary_key_is_some_value>"

I would certainly prefer the former to be the default over the (current)
latter setting.

-krish

> Cedric,
>
> Actually, I believe you provide the following:
>
>     Exclusive concurrency (pessimistic locking at the container level)

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to