Bug #3577

String fields in the db are limited to 255 characters but users demand bigger sizes and there is not warnings

Added by Jesús García Crespo about 10 years ago. Updated over 7 years ago.

Status:VerifiedStart date:
Priority:HighDue date:
Assignee:David Juhasz% Done:

0%

Category:-
Target version:Release 1.3
Google Code Legacy ID:atom-1628 Tested version:
Sponsored: Requires documentation:

Description

To reproduce this error: ========================
1) Create a new information object
2) Insert a title value bigger than 255 characters

Resulting error: ================
The title is truncated to the limit of the field in the database: 255 characters and the user is not being warned.

Expected result: ================
In my opinion, we should increase the size limit to 512 characters for some fields like limit (this requires to modify the data schema). In the other hand, we should warn users about size limits. Set a size limit in the <input/> HTML tag would be the easyer solution.

[g] Legacy categories: Form validation, Form validation

1.3_title.png (293 KB) Jessica Bushey, 12/01/2012 03:28 AM

1024screen.png (85.3 KB) Jessica Bushey, 12/01/2012 03:28 AM

History

#1 Updated by Jesús García Crespo almost 10 years ago

  • Priority changed from Medium to Low

[g] Labels added: Priority-Low
[g] Labels removed: Priority-Medium

#2 Updated by David Juhasz almost 10 years ago

Let's use the LONGVARCHAR/TEXT field type for columns that require more than 255 chars so we don't run into the same problem with an arbitrary value like 512 chars - hopefully 65,536 chars is enough ;).

The actual memory use for all these field types is determined by the amount of data stored so there's no extra overhead for a larger char limit afaik.

#3 Updated by Evelyn McLellan almost 10 years ago

  • Target version set to Release 1.2

Moved to 1.2.

[g] Labels added: Milestone-Release-1.2

#4 Updated by David Juhasz over 8 years ago

  • Target version set to Release 1.3

Roll over to Release 1.3

[g] Labels added: Milestone-Release-1.3

#5 Updated by David Juhasz about 8 years ago

  • Priority changed from Low to High

This is a minor change, let's try and get it in for Release 1.3

[g] Labels added: Priority-High
[g] Labels removed: Priority-Low

#6 Updated by David Juhasz about 8 years ago

  • Status changed from New to QA/Review

Fixed in r11837. Data migration added in r11838.

[g] New owner: David Juhasz

#7 Updated by Jessica Bushey about 8 years ago

  • Status changed from QA/Review to Verified
  • File 1.3_title.png added

Unlimited characters available in Title field. Yes.
No warnings or limits given.

NOTE: Is it possible to use an ellipse in this data field? I have attached a screen shot of what happens when you browse information objects that have a long title. It would be better with an ellipse that could be expanded and contracted.

#8 Updated by David Juhasz about 8 years ago

  • Status changed from Verified to QA/Review

Re-reading http://dev.mysql.com/doc/refman/5.0/en/blob.html, there are performance considerations with switching to unlimited (TEXT) fields in the database that I didn't know about. I've switched back to a limited number of characters (VARCHAR) but increased the width to 1024 chars.

#9 Updated by David Juhasz about 8 years ago

See r11847.

#10 Updated by Jessica Bushey about 8 years ago

I tested and can confirm the limited characters; however, I can't confirm the character width increase to 1024.

See screenshot which looks identical to the earlier screenshot; but, is shorter due to the limited number of characters.

#11 Updated by Jesús García Crespo about 8 years ago

  • Status changed from Feedback to Verified

Also available in: Atom PDF