Paul DuBois wrote:
> At 12:00 +1000 9/9/03, Daniel Kasak wrote:
>
>> It's been suggested that I add 'enable-locking' to the [mysqld]
>> section of my.cnf.
>
>
> You might want to reconsider. It's disabled by default on all systems
> as of MySQL 4, and was disable by default before that on Linux.
I see.
I had always thought that locking would be a good idea for us.
We have 40 or so people on a LAN, running MS Access XP front-ends, and
some web clients as well. Many of the Access front-ends are in
'datasheet' mode - ie where users can see multiple records on the one
screen.
Why is locking disabled and not recommended? I had a look on the web
site, and saw a few pages on locking, but didn't find any mention of
locking being disabled.
I found the source of the '--skip-locking' switch - it was in the
mysqld_safe scripts. Thanks for that :)
I haven't removed it yet - I'm thinking about it. See above...
--
Daniel Kasak
IT Developer
* NUS Consulting Group*
Level 18, 168 Walker Street
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: dkasak@stripped
website: http://www.nusconsulting.com
