Hi all.
We're using mysql 3.22, on a Red Hat Linux 6.2 system. We're also
accessing the data through MyODBC, from Windows. The mysqld is started
with the skip-locking feature activated
The problem is that we are experiencing index corruption when we access
both with the clients and with myODBC. We've been suggested to remove
the skip-locking feature but, according to the description of the
feature itself, it should not be involved in this problem.
Can someone provide an exact description of the skip-locking feature?
Can someone says if there're any known problem with mysql and myodbc
concurrent access?
Thanks you all in advance
Marco
--
Marco Bizzarri - Responsabile Tecnico - Icube S.r.l.
Sede: Via Ridolfi 15 - 56124 Pisa (PI), Italia
E-mail: [EMAIL PROTECTED] WWW: www.icube.it
Tel: (+39) 050 97 02 07 Fax: (+39) 050 31 36 588
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
