Lock wait timeout / Repeating in Class::DBI

[prev] [thread] [next] [Date index for 2005/04/28]

From: Ian McDonald-ONLINE
Subject: Lock wait timeout / Repeating in Class::DBI
Date: 15:20 on 28 Apr 2005
Hi,

In the case of lock wait timeout, it might be useful to wrap all INSERT
and UPDATE commands in something which tried the connection a fixed
number of times in the hope the lock timed out; has anyone already done
this?

Or found a not-obvious-to-me reason why this isn't a good idea?

Ta,

Ian

--
Dr Ian McDonald
Software Engineer, Interactive Drama & Entertainment
A300, 56-58 Wood Lane (CH), London W12 7SB
020 822 56162
ian.mcdonald@xxx.xx.xx / "Ian McDonald-ONLINE" (not "Ian MacDonald")



http://www.bbc.co.uk/

This e-mail (and any attachments) is confidential and may contain
personal views which are not the views of the BBC unless specifically
stated.
If you have received it in error, please delete it from your system.=20
Do not use, copy or disclose the information in any way nor act in
reliance on it and notify the sender immediately. Please note that the
BBC monitors e-mails sent or received.=20
Further communication will signify your consent to this.

Lock wait timeout / Repeating in Class::DBI
Ian McDonald-ONLINE 15:20 on 28 Apr 2005

Re: Lock wait timeout / Repeating in Class::DBI
Perrin Harkins 15:37 on 28 Apr 2005

Generated at 10:24 on 04 May 2005 by mariachi v0.52