On Wed, 17 Apr 2013 15:39:50 +0200
"J Trahair" wrote:
> I'm looking for a way to ensure other users aren't allowed to write
> to the database during this quarter-second period.
That might work for you this time, but it doesn't scale well;
historically that's why
Don't forget that your "other" applications will need to extend their
connection time outs, otherwise, while "this" application has the lock, the
"other" applications will time out and throw errors.
On Wed, Apr 17, 2013 at 9:43 AM, Simon Davies
wrote:
> On 17 April
On 17 April 2013 14:39, J Trahair wrote:
> Hi everyone
>
> Can my application lock the database for its own exclusive use at the
> beginning of a series of INSERTs UPDATEs and SELECTs, then unlock it again
> afterwards? I've read about the five locking states
Hi everyone
Can my application lock the database for its own exclusive use at the beginning
of a series of INSERTs UPDATEs and SELECTs, then unlock it again afterwards?
I've read about the five locking states (unlocked, shared, etc.) but I assume
the dll handles all that at INSERT or UPDATE
4 matches
Mail list logo