View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003789 | mantisbt | bugtracker | public | 2004-04-29 03:20 | 2014-10-14 16:21 |
Reporter | manulamb | Assigned To | grangeway | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Summary | 0003789: field possible_values in table mantis_custom_fields_table | ||||
Description | In my local installation, I have modified this field to BLOB instead of VARCHAR(255), otherwise it cannot hold enough values. Everything seems to be working fine... maybe you can apply this modification to the production release also? | ||||
Tags | No tags attached. | ||||
If your custom values are defined in a table or in another source, you can know use custom functions to calculate the possible values at runtime. In this case, the 255 length limitation is fixed. See 0005180 for more details. |
|
Ideally we should have an option to store a custom field as the same data type we store description. |
|
possible_values was changed from varchar(255) in a previous release. |
|