Bug #17410 "Obtaining Information About Partitions" section contains incorrect info
| Submitted: | 15 Feb 2006 2:55 | Modified: | 17 Feb 2006 13:44 |
|---|---|---|---|
| Reporter: | Sergey Petrunya | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
| Version: | OS: | ||
| Assigned to: | Jon Stephens | CPU Architecture: | Any |
[15 Feb 2006 2:55]
Sergey Petrunya
[17 Feb 2006 13:44]
Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant product(s). Additional info: 1. This was true when I tested it in the course of writing the Partitioning chapter (I know some people think I just make stuff up, but I really don't). Since no bug was ever filed and it wasn't covered in the WL, I had no way of knowing that this was not expected behaviour. I've cut this paragraph from the chapter. 2. My feeling was that if I didn't say something like this, then someone would complain that I'd not covered what happens when you try this statement against a non-partitioned table. ;) 3. Again, this was what I uncovered during tests with a pre-release build. (I can't test the behaviour of a release that's not yet been released.) Since you've provided a working counterexample (almost identical to one which I tried and which did NOT work when I wrote the chapter), I've cut the offending paragraph. Thanks for bringing my attention to these issues!
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.049 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.