Just a little side note,
The table engine needs to be InnoDB or the transaction will not have effect,
The behavior may differs also according to the isolation level,
That will apply a lock on all records because no where is specified, which
its not very common.
Regards,
Claudio
On Jun 16, 2011 8:
adarsh.sha...@orkash.com
> To: mysql@lists.mysql.com
> Subject: Re: Query on wait_timeout
>
> Thanks Suresh but I find it very difficult to implement it :-
>
> Suresh Kuna wrote:
> >
> > Try this out:-)
> >
> > Below are the steps to generate a deadlock so that the
Thanks Suresh but I find it very difficult to implement it :-
Suresh Kuna wrote:
Try this out:-)
Below are the steps to generate a deadlock so that the behaviour of a
deadlock can be illustrated:
-- 1) Create Objects for Deadlock Example
USE TEMPDB
Is I have to create temdb database as be
Try this out:-)
Below are the steps to generate a deadlock so that the behaviour of a
deadlock can be illustrated:
-- 1) Create Objects for Deadlock Example
USE TEMPDB
CREATE TABLE dbo.foo (col1 INT)
INSERT dbo.foo SELECT 1
CREATE TABLE dbo.bar (col1 INT)
INSERT dbo.bar SELECT 1
-- 2) Run in f
How we can create a deadlock manually to test this problem.
Thanks
Suresh Kuna wrote:
Good question Yogesh, I can say the best solution is
Create a deadlock and test it, you will come to know more about it.
On Wed, Jun 15, 2011 at 3:38 PM, Yogesh Kore wrote:
Hi,
Small doubt for wait_ti
Good question Yogesh, I can say the best solution is
Create a deadlock and test it, you will come to know more about it.
On Wed, Jun 15, 2011 at 3:38 PM, Yogesh Kore wrote:
> Hi,
>
> Small doubt for wait_timeout.
>
> If my wait_timeout is set for 180 seconds and if any deadlock occures and
> bo
