“If debugging is the process of removing bugs, then programming must be the process of putting them in.” – Edsger Dijkstra
This is the Bug Tracking System for the Flyspray project. This is not a demo! Before opening a new task, please read the guidelines!
Do not issue bugs reports against versions earlier than 0.9.9.6
Security problem? Check the security section.
FS#1623 - Version: too long for field
Opened by Pete (Pete) - Thursday, 14 January 2010, 20:24 GMT+1
Last edited by Florian Schmitz (Floele) - Thursday, 08 December 2011, 18:02 GMT+1
|
DetailsIf entering too much information into the version (at the admin or project level) get this error: Query {INSERT INTO `flyspray_list_version` (project_id, version_name, list_position, show_in_list, version_tense) VALUES (?, ?, ?, ?, ?)} with params {27,resolved in current release,38,1,2} Failed! (Data too long for column 'version_name' at row 1) Need to add a limit to what can be typed in the text box to prevent this error (or however you see fit). |
Thursday, 08 December 2011, 18:02 GMT+1
Reason for closing: Not a bug
Pete, When I go to enter a version it limits what I can type to 40 characters. It seems that you are able to go over the 40 characters. Just to double check you are going to (Admin Toolbox => Versions) Then in the input box you are causing the DB error? If you are still having the error use the following command to get the bleeding edge version of Flyspray. svn co https://flyspray.svn.sourceforge.net/svnroot/flyspray/branches/0.9.9/ flyspray Once you have the code can you try to duplicate the bug one more time? Thank you!
Sorry, we no longer use this product. We switched over to [[http://www.bugnetproject.com/|BugNET]]
No problem! Sorry Flyspray wasn't able to fulfill all your needs I call for closure of this. I can't reproduce the issue, as it is solved Client side.
This bug still exists. It is possible to make this error happen when entering too match data. The code should cut the string, and the UI should prevent entering such long data (max length text field). It should be fixed even if the reporter of this issue no longer uses FS.
Maybe I was trying to break the wrong form? If you go to the Administrator Toolbox and then go to versions the field listnamenew limits me to 40 chars and so does listname0? Maybe if I had more versions I could reproduce the error? Or I am completely off on what is wrong
OK, seems like our DB was not upgraded yet. Official size is 40 chars, so I guess it's OK.