How to handle database concurrency?

[Marcus Leon]

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

 

[zero]

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.

 

[maurizio.lattuada]

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

 

[karlheinz klingbeil]

(e-mail address removed) 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.