Bug #10651 Views: var_samp() looks like var_pop()

Description:
When I create a view which refers to var_samp(), MySQL translates it to variance().
That's not correct. Although var_pop() is the same a variance(), var_samp() is not.
So, when "select var_samp(...) from base_table" and "select var_samp(...)
from view_made_with_select_star_from_base_table" deliver different results.

How to repeat:
mysql> create table t86 (s1 int);
Query OK, 0 rows affected (0.01 sec)

mysql> create view v86 as select var_samp(s1) from t86;
Query OK, 0 rows affected (0.01 sec)

mysql> show create view v86;
+------+------------------------------------------------------------------------------------------------------------------------------+
| View | Create View          |
+------+------------------------------------------------------------------------------------------------------------------------------+
| v86  | CREATE ALGORITHM=UNDEFINED VIEW `mysql4`.`v86` AS select variance(`mysql4`.`t86`.`s1`) AS `var_samp(s1)` from `mysql4`.`t86` |
+------+------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.01 sec)

Thank you for the bug report.

ChangeSet
  1.2011 05/06/24 22:02:19 bell@sanja.is.com.ua +3 -0
  fixed var_samp printing (BUG#10651)

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/26418

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/26495

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/26621

pushed to 5.0.9

Noted in 5.0.9 changelog.