into  weblab.(none):/home/marcsql/TREE/mysql-5.1-22687

According to some internal communication, these two functions are place
holders for future enhancements. Because they use a variable number of
parameters, the implementation defined a reserved keyword for them in the
parser grammar.

Unfortunately, doing so creates a bug similar to Bug 21114 reported for the
function FORMAT.

In the 5.1 code base, due to improvements in the code implemented with bug
21114, having a reserved keyword for functions with a variable number of
arguments is not needed any more by the implementation.

As a result, this fix removes the place-holder implementation, and removes
the unnecessary reserved keywords. Should the functions UNIQUE_USERS and
GROUP_UNIQUE_USERS be finally implemented in a later release, the
implementation should sub class Create_native_func in sql/item_create.cc.
For example, see the class Create_func_concat.

into  bodhi.local:/opt/local/work/mysql-5.1-runtime

into  weblab.(none):/home/marcsql/TREE/mysql-5.1-25183

into  weblab.(none):/home/marcsql/TREE/mysql-5.1-25302

into  mysql.com:/d2/hf/mr10/my51-mr10

into  moonlight.home:/home/tomash/src/mysql_ab/mysql-5.1-bug23443

into  moonlight.home:/home/tomash/src/mysql_ab/mysql-5.0-bug23443

into  moonlight.home:/home/tomash/src/mysql_ab/mysql-4.1-bug23443

           server

The problem was that when memory was exhausted HEAP engine could crash
(GROUP BY uses HEAP TABLE).  Alternatively, if SET was used, it could
report an error "You may only use constant expressions with SET" instead
of "Out of memory (Needed NNNNNN bytes)".

The solution is:
 - pass MY_WME to (some) calls to my_malloc() to get correct message.
 - fix heap_write() so that the first key is skipped during cleanup
   on ENOMEM because it wasn't inserted and doesn't have to be
   deleted.

No test case is provided because we can't test out-of-memory behaviour
in our current test framework.

Cleaning up warning for windows. Innodb is compiled but disable on Windows, so it should be fine. NDB wasn't compiled in, which is what caused the issue. 

into  zim.(none):/home/brian/mysql/merge-5.1

The CSV format has always relied on numbers being quoted, which doesn't always happen. This fixes that so that numbers can now be unquoted (and the output does this as well so that the log takes up less space). 

into  bk-internal.mysql.com:/data0/bk/mysql-5.1-arch

Split out the hidden class from the ha_tina file (probably should have just deleted it...) but this is a bit better. 

This fix corrects build issues introduced by WL#3031:

- In the SQL grammar, 'USER' is a SQL 2003 reserved keyword,
and therefore should not be part of the keyword production.

- In sql/sql_parse.cc, the code for CREATE SERVER and ALTER SERVER
was not using proper format strings in the DBUG_PRINT statements.

into  mysql.com:/d2/hf/common/my51-common

into  mysql.com:/d2/hf/common/my51-common

into  mysql.com:/d2/hf/common/my50-common

into  weblab.(none):/home/marcsql/TREE/mysql-5.1-merge

into  trift2.:/MySQL/M51/mysql-5.1

    Delete compiler-specific flag setting - it makes builds break.

into  mysql.com:/d2/hf/common/my51-common

into  mysql.com:/d2/hf/common/my50-common

into  mysql.com:/d2/hf/common/my51-common

into  mysql.com:/d2/hf/common/my50-common

into  mysql.com:/d2/hf/common/my50-common

into  mysql.com:/home/kent/bk/main/mysql-5.1

  Temporary work around for bug#25359