Bug #26038 | X() value of empty NOT NULL POINT is neither NULL nor NOT NULL | ||
---|---|---|---|
Submitted: | 2 Feb 2007 11:27 | Modified: | 15 Mar 2007 15:27 |
Reporter: | Peter Brodersen (Candidate Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.0.32-Dotdeb_1.dotdeb.1-log, 4.1 BK, 5.1 BK | OS: | Linux (Linux) |
Assigned to: | Ramil Kalimullin | CPU Architecture: | Any |
[2 Feb 2007 11:27]
Peter Brodersen
[2 Feb 2007 12:30]
Sveta Smirnova
Thank you for the report. Verified as described.
[21 Feb 2007 10:45]
Bugs System
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/commits/20254 ChangeSet@1.2609, 2007-02-21 14:45:19+04:00, ramil@mysql.com +6 -0 Fix for bug #26038: X() value of empty NOT NULL POINT is neither NULL nor NOT NULL Having maybe_null flag unset for geometry/spatial functions leads to wrong Item_func_isnull::val_int()'s results. Fix: set maybe_null flag and add is_null() methods.
[21 Feb 2007 11:05]
Alexander Barkov
I think the patch is ok to push.
[8 Mar 2007 20:14]
Timothy Smith
pushed to 4.1.23, 5.0.38, 5.1.17
[15 Mar 2007 15:27]
Paul DuBois
Noted in 4.1.23, 5.0.38, 5.1.17 changelogs. X() IS NULL and Y() IS NULL comparisons failed when X() and Y() returned NULL.