How to handle database concurrency?

Thread view:

Marcus Leon - 11 Jan 2006 21:03 GMT

We have some database data that multiple users may update. What is the
best concurrency strategy? Should we use EJBs with the concurrency
setting set to "Exclusive"? Or should we just use JDBC with
transactions and let the database (Oracle) handle concurrency?

Thanks

Reply to this Message

zero - 12 Jan 2006 01:08 GMT

"Marcus Leon" <marcus.leon@gmail.com> wrote in news:1137013436.644704.63700
@f14g2000cwb.googlegroups.com:

> We have some database data that multiple users may update. What is the
> best concurrency strategy? Should we use EJBs with the concurrency
> setting set to "Exclusive"? Or should we just use JDBC with
> transactions and let the database (Oracle) handle concurrency?
>
> Thanks

If you're using an almighty database like Oracle anyway, I'd suggest
letting it do all the work.

Signature

Beware the False Authority Syndrome

Reply to this Message

maurizio.lattuada@gmail.com - 12 Jan 2006 13:21 GMT

i agree with zero: with databases like oracle, sql server, you should
let them to manage concurrency.
If you use mysql don't forget to set tables with type 'InnoDB'. Default
is 'MyIsam', but this one doesn't take care about concurrency

Reply to this Message

karlheinz klingbeil - 12 Jan 2006 16:34 GMT

maurizio.lattuada@gmail.com schrub am Donnerstag, 12.
Januar 2006 14:21 folgendes:

> i agree with zero: with databases like oracle, sql
> server, you should let them to manage concurrency.
> If you use mysql don't forget to set tables with type
> 'InnoDB'. Default is 'MyIsam', but this one doesn't
> take care about concurrency

This is not quite right. MyIsam also supports
concurrency, but not Transactions, which are available
only with InnoDB tables.

Signature

greetz Karlheinz Klingbeil (lunqual)
http://www.lunqual.de oder http:www.lunqual.net

Reply to this Message

How to handle database concurrency?

Free Magazines