Bug #6553 | STRICT mode: Bad spatial values don't cause errors | ||
---|---|---|---|
Submitted: | 10 Nov 2004 17:02 | Modified: | 30 Apr 2005 13:31 |
Reporter: | Paul DuBois | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.0.x | OS: | |
Assigned to: | Alexey Botchkov | CPU Architecture: | Any |
[10 Nov 2004 17:02]
Paul DuBois
[10 Nov 2004 17:36]
MySQL Verification Team
Verified with 5.0.2-alpha-debug-log
[14 Mar 2005 12:14]
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/internals/22994
[28 Apr 2005 13:59]
Michael Widenius
Still some more work to be done on the patch: - Better error message If possible (if not now, then at least later): - For wrong values in not strict mode, insert null or "" into the geometry field. (This is to avoid cases where only a part of the rows in a set are inserted)
[28 Apr 2005 14:03]
Michael Widenius
Still some more work to be done on the patch: - Better error message If possible (if not now, then at least later): - For wrong values in not strict mode, insert null or "" into the geometry field. (This is to avoid cases where only a part of the rows in a set are inserted)
[30 Apr 2005 13:31]
Alexey Botchkov
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bugfix, yourself. More information about accessing the source trees is available at http://www.mysql.com/doc/en/Installing_source_tree.html