Anyway - reported this as a 4.1.2 bug (on the grounds that it used to work in 4.0.17) and have just been told the bug was in 4.0.17, which should not have allowed this behaviour!
From: "Martijn Tonies" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>,<[EMAIL PROTECTED]>
Subject: Re: Error 1250 Table from one of the SELECT's cannot be used in global ORDER clause
Date: Wed, 16 Jun 2004 09:06:12 +0200
Hi Dave,
> Unfortunately species_id is a column I am using for joining so I need the
> fully qualified name both in the SELECT and the ORDER BY.
What does the join have to do with the ORDER BY?
With regards,
Martijn Tonies Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL Server. Upscene Productions http://www.upscene.com
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]