Krish,
I agree. I was beginning to wonder if I'd missed something fundamental about
EJBs because that's exactly the kind of code that 4GL client/server tools
such as Oracle Forms* have been able to generate for many years, and their
experience suggests that it certainly can perform scalably for large
interactive transactional user populations. (Isn't it great how we in IT
keep reinventing the same ideas?) It's a little more expensive on memory
(since you have to retain the original values of the fetched fields), but
not terribly so.
Carl Zetie
*and many others, of course. Oracle Forms just happens to be one I know
best.
> -----Original Message-----
> From: Krishnan Subramanian [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 28, 2001 4:02 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [EJB-INT] Are Entity Beans(CMP/BMP) really necessary???
>
>
> 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
>
===========================================================================
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".
