View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0010370 | mantisbt | custom fields | public | 2009-04-22 09:46 | 2019-12-03 05:41 |
Reporter | jonathh | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | always |
Status | acknowledged | Resolution | open | ||
Summary | 0010370: Max field length not respected. | ||||
Description | I applied a max field length for a custom field of a string to 1024 (default of 256) when i enter my text i can indeed enter more characters but when you submit it is truncated. Also the default value field isn't updated so you couldn't have a 1025 charactor long default value? | ||||
Tags | No tags attached. | ||||
"It's not a bug, it's a feature..." Custom fields are unable to have maximum lengths longer than 255 due to the way the custem field schema has been designed/defined. Some database types do not support VARCHAR fields longer than 255 characters, and for some reason MantisBT chose to use a VARCHAR field rather than a TEXT field. I would disagree with that decision, but that's just how it is, unless Paul/Daryn decides to fix that inn their eventual updates to custom fields... |
|
Man.. that sucks. Is it hard to change the schema? Would the code that wraps around it need changing? - I think maybe not as everything else respects the size it is just truncated on POST. We wanted to use it to store a 'client name' drop down. We wont get many clients in a list with that sort of limitation! |
|
Is this a duplicate of 0008518 ? |
|
@jonathh, the following wiki page should help you to achieve what you need. Let us know if it works for you. |
|
@vboctor: Which wiki page do you mean? |
|