Hi, may be I wasn't clear enough. With concurrency I meant2 threads each doing the following operations: 1. Start transaction. 2. insert row 3. insert another row 4. commit/rollback transaction
In this situation is the transaction isolation guaranteed? > Is there any best practice? == speed up application end avoid loading every > time the same config files -----Messaggio originale----- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per conto di Larry Meadors Inviato: venerdì 5 gennaio 2007 16.19 A: user-java@ibatis.apache.org Oggetto: Re: SqlMapClient multithread applications On 1/5/07, De Gaetano Giuseppe <[EMAIL PROTECTED]> wrote: > If the application is multithread and each thread uses the same client will > I have some problem? Should be fine. > > Is the iBatis engine handling the concurrency or should I care? What type of concurrency? If two threads update the same row in the database, the last one in wins. iBATIS does not and will not likely ever deal with that sort of thing. > Is there any best practice? Sorry if i am being dense, but for what? Larry
