Cedric Beust wrote:
>
> > From: A mailing list for Enterprise JavaBeans development
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Jonathan K. Weedon
>
> > Database based optimistic concurrency
> >
> > This corrupts the database, if done without verified updates
>
> No.
>
> Or rather, if it corrupts the database, pick another database vendor.
Most customers I am aware of will throw out their app. server well before they
throw out their DB server. If the app. server can't provide decent support for
optimistic concurrency control, it won't be long until people running ECperf
find out which products they really should be using to get decent scalability :-)
> The database is in charge of making sure the update is valid. If it is not,
> it should be rolled back.
>
> > So, you have a choice between unscalable (pessimistic locking, either
> > in an unclustered container, or in the central database) or incorrect
> > (due to unverified updates).
>
> Come on, Jonathan...
>
> --
> Cedric
>
> ===========================================================================
> 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".
--
________________________________________________________________________________
Evan Ireland Sybase EAServer Engineering [EMAIL PROTECTED]
Wellington, New Zealand +64 4 934-5856
===========================================================================
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".
