Thanks Gerald,
I finally figured that out, from what I understand, when locking and the given
table is set to 'WRITE' this includes 'READ' too. so I only needed to use the
table once :)
Cheers,
>>On Fri, 03 Aug 2001 14:31:00 -0500, Gerald Clark <[EMAIL PROTECTED]>
> wrote:
>>
>>> Hi All,
>>>
>>> Was hoping some one maybe able to explain this error when attempting to LOCK
>>> MySQL tables for READ and WRITE:
>>>
>>> Error Encountered:
>>> Unable to LOCK tables.
>>>
>>> Error: Not unique table/alias: 'members'
>>>
>>> The correct database has been connected to, and the members table is a valid
>>> table. It's executed via Perl coding:
>>> $dbh->do("LOCK TABLES members READ, members WRITE, optin WRITE");
>>>
>>> is this syntax incorrect??
>>
>>No. You included members twice. Thus, it is not unique.
>>If you are going to write to it use write, otherwise use read.
Mike(mickalo)Blezien
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Thunder Rain Internet Publishing
Providing Internet Solutions that work!
http://www.thunder-rain.com
Tel: 1(225)686-2002
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
---------------------------------------------------------------------
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
