I can't help directly with the error message (the warning seems fairly
harmless), but may I inquire why you are building MySQL instead of using one
of the prepared binaries? Compiling under OS/X can be pretty harrowing.
- michael dykman
On Sat, Oct 8, 2011 at 2:49 AM, Peter Schrock wrote:
> I
Several MySQL fora, including all the Usage fora, have been overrun by
spam to the point of unusability, with no sign of effective remediation.
This gives the impression that a process of letting MySQL die of
neglect has begun.
PB
--
MySQL General Mailing List
For list archives: http://lists
I can understand your point, however, as stated, I am using a ppc
architecture and am not afforded the luxury of binaries in the most up to
date versions. I know using 5.1.59 isn't the most up to date, but I was also
having issues with the most current version. I might start with the most
current b
Does the optimizer look into function called from query?
In my queries the expression (SELECT hwyl FROM Stock) / (SELECT regularPayment
FROM Stock), where Stock is a one-record table, often is repeated. The
optimizer sees that, and makes the ratio a constant, and I can afford to be
clear. If th
I think the only clues the optimizer consults with regard to UDFs is the
'characteristic' provided at the time you create the routine.
from http://dev.mysql.com/doc/refman/5.0/en/create-procedure.html
*
*
*characteristic*:
COMMENT '*string*'
| LANGUAGE SQL
| [NOT] DETERMINISTIC
| { CON
