Re: Null variables in functions handled incorrectly in WHERE clause (?)
Indrek Siitan <[email protected]>
| Newsgroups | gmane.comp.db.mysql.bugs |
|---|---|
| Message-ID | <BB88D450.2FB17%[email protected]> |
Hi, > When I use an undefined variable as an argument to a function (e.g. PASSWORD() > or UPPER()) in a WHERE clause, rows are returned when it appears they should > not be. If NULL is passed directly, no rows are returned as expected. When a > null variable is used, however, rows are returned erroneously: Thank you for an excellent bug report. I have entered this into the bug database now, where you can track its progress. The bug id is #1271, and the URL to view it is: http://bugs.mysql.com/bug.php?id=1271 Rgds, Indrek -- | Indrek Siitan, MySQL AB, Support Engineer & Bugmaster | Uuemõisa, Haapsalu, Estonia +- | Are you MySQL Certified? http://www.mysql.com/certification/ -- -- MySQL Bugs Mailing List For list archives: http://lists.mysql.com/bugs To unsubscribe: http://lists.mysql.com/[email protected]