Bug #6796 | Triggers and stored procedures allow meaningless AVG() | ||
---|---|---|---|
Submitted: | 24 Nov 2004 14:27 | Modified: | 29 Sep 2008 20:55 |
Reporter: | Peter Gulutzan | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.0.2-alpha-debug | OS: | Linux (SuSE 8.2) |
Assigned to: | CPU Architecture: | Any |
[24 Nov 2004 14:27]
Peter Gulutzan
[25 Nov 2004 10:14]
Per-Erik Martin
This is not a stored procedure or trigger specific issue: mysql> set @x = AVG(@y); Query OK, 0 rows affected (0.00 sec) mysql> select @x; +------+ | @x | +------+ | NULL | +------+ 1 row in set (0.00 sec) mysql> set @y = 3; Query OK, 0 rows affected (0.00 sec) mysql> set @x = AVG(@y); Query OK, 0 rows affected (0.00 sec) mysql> select @x; +------+ | @x | +------+ | NULL | +------+ 1 row in set (0.00 sec) mysql>
[29 Sep 2008 20:23]
Konstantin Osipov
I can't repeat it with 6.0.8, needs to be re-verified.
[29 Sep 2008 20:55]
MySQL Verification Team
I couldn't repeat too.