Menu
▾
▴
#4923 (ok 4.4.8) Limits table comments to 60 characters
In the options pane of table operations, table comments can be set. Unfortunately, their length is limited to 60 characters via maxlength. This was the length limit prior to MySQL 5.5.3, but newer servers support 2048 characters, which is extremely useful. MySQL Workbench allows making use of the server's actual limit. See https://docs.oracle.com/cd/E17952_01/workbench-relnotes-en/wb-news-5-2-37.html for reference.
By the way, something is wrong with your tracker's Milestone field (sets to 3.5.1 by default).
Thanks, I had not noticed that we can set a default milestone.
Milestone 4.4.7 should not be set since that version is already released (see https://sourceforge.net/p/forge/documentation/Tickets/ about meaning). I strongly recommend to let this field empty by default.
By the way, this problem affects phpMyAdmin 4.4.6.
For us, milestone means the version on which the bug occurs. Also, I cannot see how to leave the milestone empty by default. Maybe we would need a fictitious milestone called "Choose the version".
I have never seen "Milestone" used to track affected version. I think doing so is quite misleading - this could lead users to conclude the project misses "deadlines", that a fix is coming quickly or even that an issue is already solved.
I would really advise to stop using Milestone for version tracking. I am very surprised to see that SourceForge appears to lack an equivalent. Perhaps this could be achieved with a custom field of type Select.
If you really want to keep using Milestone that way, I would create a milestone as you suggest indeed (I suggest titling "Choose the version which is affected by this issue" or so, so reporters understand the field does not actually contain milestones).
Fixed with https://github.com/phpmyadmin/phpmyadmin/commit/834df9d98279be72459ef33185f79c1138ca3d60