Has anyone run into this before? Is it documented as expected behavior
somewhere, or just a bug? I have a statement like this in a stored
procedure (vNewPwd is a SHA1 hash value which is a 40-digit hex number):

IF HEX ( UNHEX( vNewPwd )) != vNewPwd THEN
---
END IF;

The procedure compiles OK, but calling it gives me the rather strange
runtime error "Function myschema.HEX does not exist". (?!?! -- of course
it doesn't exist because there is a perfectly good built-in HEX()
function in MySQL...)

If I remove the spaces and put parentheses around the function calls, it
works:

IF (HEX(UNHEX(vNewPwd)) != vNewPwd) THEN
---
END IF;

However, in other languages I like to increase readability by inserting
spaces sometimes. Or is it just the extra parentheses that make a
difference?

Robert Hairgrove wrote:
Nope, in MySQL, the spaces make a difference, also.


--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex (AT) attglobal (DOT) net
==================

Robert Hairgrove wrote:
I have found that MySQL will not work with spaces between parentheses
and contents.

Like it or not, that's the way it is.

Robert Hairgrove <rhairgrove (AT) bigfoot (DOT) com> wrote:

Documented behavior.

With default settings MySQL requires that no space is between the
function name and the opening parenthesis. This allows to use function
names as identifiers (this is sometimes important because new versions
can add new functions and would then break old applications).

However there exists the IGNORE_SPACE SQL mode that allows space after
the function name. See

http://dev.mysql.com/doc/refman/5.1/...esolution.html
http://dev.mysql.com/doc/refman/5.1/...-sql-mode.html


XL