Hi!
On Oct 05, Ville Mattila wrote:
> Hi there,
>
> I have noticed a few things that cause problems when using table aliases
> (SELECT ... FROM table1 t1, table2 t2):
>
> 1) Fulltext index queries don't work. I tried to complete a following query:
>
> a)
> SELECT p.*, c.name AS categoryname FROM products p, categories c WHERE
> MATCH(p.name,p.description) AGAINST('keywords');
>
> It will cause an error that there is no FULLTEXT index matching the query.
Hmm, I wasn't able to repeat it.
Could you submit the complete test case at http://bugs.mysql.com/ ?
> b)
> SELECT products.*, categories.name AS categoryname FROM products,
> categories WHERE MATCH(products.name,products.description)
> AGAINST('keywords');
>
> works anyway well.
>
> 2) Table name locking doesn't work with table aliases - or works, but
> eatch alias must be locked separately and the final queries must contain
> same aliases. Examples a and b cause both an error that tables are not
> locked. Examples c and d work well.
Right.
This is how, according to the manual, LOCK TABLES should work.
Regards,
Sergei
--
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik <[EMAIL PROTECTED]>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Senior Software Developer
/_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
<___/ www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
