Hello,

I have a site which is to be mentioned on a radio programme and just
might have lots of users accessing the site following this broadcast.

There is javascript/php which adds data to MySQL - is there any need
to lock/unlock the table each time or does MySQL itself take care of
large numbers of concurrent users?

Thanks

Geoff

On Fri, 16 May 2008 08:51:37 +0100, Geoff Cox <gcox@freeuk.notcom>
wrote:

grief! LOCK not lack ....

Geoff

On 16 May, 07:51, Geoff Cox <g...@freeuk.notcom> wrote:
> Hello,
>
> I have a site which is to be mentioned on a radio programme and just
> might have lots of users accessing the site following this broadcast.
>
> There is javascript/php which adds data to MySQL - is there any need
> to lock/unlock the table each time or does MySQL itself take care of
> large numbers of concurrent users?

If all you are doing is adding data to a table then that is fine.
Locking tables is only required for transactional type processing,
when the InnoDB engine is not available.

On Fri, 16 May 2008 02:23:12 -0700 (PDT), Captain Paralytic
<paul_lautman@yahoo.com> wrote:

>On 16 May, 07:51, Geoff Cox <g...@freeuk.notcom> wrote:
>> Hello,
>>
>> I have a site which is to be mentioned on a radio programme and just
>> might have lots of users accessing the site following this broadcast.
>>
>> There is javascript/php which adds data to MySQL - is there any need
>> to lock/unlock the table each time or does MySQL itself take care of
>> large numbers of concurrent users?
>
>If all you are doing is adding data to a table then that is fine.
>Locking tables is only required for transactional type processing,
>when the InnoDB engine is not available.

Paul,

Thanks for the info. One less problem!

Cheers

Geoff