Bug #58075 | Add MAX_NUM_XXX to three enum types | ||
---|---|---|---|
Submitted: | 9 Nov 2010 8:59 | Modified: | 14 Jan 2011 13:59 |
Reporter: | Magnus Blåudd | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.5.7-rc | OS: | Any |
Assigned to: | Magnus Blåudd | CPU Architecture: | Any |
Tags: | SEAGULL |
[9 Nov 2010 8:59]
Magnus Blåudd
[9 Nov 2010 9:07]
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/123188
[10 Nov 2010 9:00]
Gustaf Thorslund
Would it be possible to introduce this in some standard way? Like calling it END (last + 1 as in .end() in C++ is supposed to be) or <ENUM_NAME>_END. In the first case the END wound need to be prefixed with enum type when needed, but that might not hurt. Trying to see how it's done currently in the code I fail to find examples. (just looked in includes/) /Gustaf
[14 Jan 2011 13:53]
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/128764
[14 Jan 2011 13:59]
Magnus Blåudd
Have reritten ha_ndbcluster so it no longer need these enum values. Closing as won't fix.