0007094: custom_field_possible_values too short

ID	Project	Category	View Status	Date Submitted	Last Update
0007094	mantisbt	custom fields	public	2006-05-16 05:25	2007-12-20 01:37

Reporter	goldstift	Assigned To	vboctor
Priority	normal	Severity	feature	Reproducibility	always
Status	closed	Resolution	duplicate
Product Version	1.0.3

Summary	0007094: custom_field_possible_values too short
Description	if you really want to have a custom select field then the limitation of the field "possible_values" to 255 characters is too less. I changed the database field type to "text" (tested with MySQL4, 5 & Postgres8.0) and removed the 'maxlength="255"' attribute in file 'manage_custom_field_edit_page.php' on line 69. It would be nice if you could change this in your sources. I already tested the databases bevaviour and seems that an ALTER TABLE statement does not cause any data loss. By the way: Is there actually a way to contribute my source code?
Tags	No tags attached.

vboctor 2006-05-16 06:43 manager ~0012843	Attach a zip file that has all the files with the modifications. If you are also a CVS user, you can submit a diff file. Ideally the zip file should include both.

vboctor 2006-05-16 06:45 manager ~0012844	I'm wondering if using "text" would affect the performance in any way. Some DBMSes don't allow SELECT * for tables that contain text fields, and for others it will probably be slower to deal with text fields compared to varchars.

goldstift 2006-05-16 09:51 reporter ~0012846	Well ok. I don't know which DBMS should not allow SELECT *, but isn't this to be avoided anyway? I read about performance loss with this method. As I think about it a little more, it's not only the field "possible_values" which would have to be treated but also the field "default_value" and eventually mantis_custom_field_string_table.value to make it fully flexible. I made the conversion with a mysql4.1.10a database of nearly 1100 bugs and yet we don't experience any performance difference... ...but my users are a lot more patient ;-)