“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#1627 - Can't create Task. Description too long?!
Attached to Project:
Flyspray - The bug killer!
Opened by Christian Engel (Paratron) - Sunday, 21 February 2010, 20:58 GMT+1
Last edited by Florian Schmitz (Floele) - Sunday, 20 November 2011, 10:09 GMT+1
Opened by Christian Engel (Paratron) - Sunday, 21 February 2010, 20:58 GMT+1
Last edited by Florian Schmitz (Floele) - Sunday, 20 November 2011, 10:09 GMT+1
|
DetailsI set up the system, created two projects with several categories and tried now to add my first bug. It doesn't work - just says: "Data too long for column 'detailed_desc' at row 1" See my attached file for the Database-Error. 
failure.txt
(16.1 KiB)
|
This task depends upon
Closed by Florian Schmitz (Floele)
Sunday, 20 November 2011, 10:09 GMT+1
Reason for closing: Fixed in devel
Sunday, 20 November 2011, 10:09 GMT+1
Reason for closing: Fixed in devel
Okay, I figured out what created the error:
In the Description Text where some german umlauts (Ä, Ö, Ü) - which crashed the query.
More information:
If I try to create a Task with umlauts - the attached error occures and no task will be created.
If I create a task without umlauts und edit it to put umlauts into it, the same error occures, BUT the task is altered correctly.
This is ridiculous.
Finally, I figured out how to fix this:
The collation of the database was set to "latin". After I deleted all tables (and flyspray), set the collation of the db to "utf8" and reinstalled flyspray everything works fine.
Nevertheless, it isn't a desired behavior of flyspray to collapse in an errormessage if unsupported characters are entered.
hmmm Maybe FS should just have it set to utf8 by default anyway to prevent that. However, I do see the point that it shouldn't just crash but give an acceptable, user friendly message informing them what the problem is.
Although I would imagine that in this case the error is caused by the database... Although FS should never have allowed it in the first place.
yeah the same problem is with polish chars! utf8 should be definitely a default charset
mysql> SELECT default_character_set_name FROM information_schema.SCHEMATA S WHERE schema_name = "flyspray"; +----------------------------+ | default_character_set_name | +----------------------------+ | utf8 | +----------------------------+