concurrency concersn in JDBC operations?

Thread view:

Steve - 09 Aug 2007 18:47 GMT

If the web application only has JDBC insert operation, do u need to
worry about the concurrency? Let's assume the web application is just
using JDBC for database manipulation. I'm concerned if the transaction
management mechanism is necessary.

If the application has update operation, then we should make sure each
the update operation is locked if 2 user are trying to update the same
record at the same time?

Please advice. thanks!!

Reply to this Message

Arne Vajhøj - 10 Aug 2007 03:06 GMT

> If the web application only has JDBC insert operation, do u need to
> worry about the concurrency? Let's assume the web application is just
[quoted text clipped - 4 lines]
> the update operation is locked if 2 user are trying to update the same
> record at the same time?

The database should itself handle two programs/threads doing single
SQL statement operations.

If you have two programs/threads doing multiple SQL statement
operations, then you may need to use transactions and specify
an appropriate transaction isolation level.

Arne

Reply to this Message

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...