Bug #18433 Lift limitation on using variables in view definition

Description:
Subj;

Just for now i can use smth like following and it works great

How to repeat:
DELIMITER $$
CREATE FUNCTION getVar() RETURNS smallint(6) DETERMINISTIC
  return @SOME_VAR $$
DELIMITER;
--------------------------------
CREATE VIEW AS
SELECT *
  FROM some_table
 WHERE some_column = getVar();

Thank you for a feature request. I think, that current behaviour is just a bug (because of inconsistency):

mysql> select version();
+--------------+
| version()    |
+--------------+
| 5.0.25-debug |
+--------------+
1 row in set (0.00 sec)

mysql> USE test;
Database changed
mysql> create view vvvvv as select @a;
ERROR 1351 (HY000): View's SELECT contains a variable or parameter
mysql> create function geta() returns int deterministic return @a;
Query OK, 0 rows affected (0.05 sec)

mysql> create view vvvvv as select geta();
Query OK, 0 rows affected (0.01 sec)

So, either feature you asked for should be implemented, or functions used in CREATE VIEWS should be checked to NOT return any user variables also.

Bug #12760 was marked as a duplicate of this one (as this is S3).

Can i hope it would be fixed in near future?

Stealing this, related to Bug#20953

The MySQL Reference Manual says for "CREATE VIEW Syntax" that
"The SELECT statement cannot refer to system or user variables",
so it's not a bug to disallow a variable in a view definition.
And this report is not a claim that it's a big to allow a variable
in a function definition.
And inconsistency is not a bug.
I'll change this to "feature request" till somebody explains
how it's a bug.

Thank you for a valid feature request.